Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d97957acf4c781252085ec6cf9af73615f510dd7e1a62af620af5dcb3f9c0ec2

Tx prefix hash: d72b6798f001a6318811dca760859e36a257e91f83502f8816536f78f1d6daf8
Tx public key: 6bb039ff4456fcf38a49c9d76f45c2562cf692aa1d8fb93971bb759b1a189d10
Timestamp: 1732407918 Timestamp [UCT]: 2024-11-24 00:25:18 Age [y:d:h:m:s]: 00:126:07:42:47
Block: 1160326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90086 RingCT/type: yes/0
Extra: 016bb039ff4456fcf38a49c9d76f45c2562cf692aa1d8fb93971bb759b1a189d100211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfc70ffb97b8f6ea274121ee21e8154f59a600012afee46e25821060d44e0710 0.600000000000 1645971 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1160336, "vin": [ { "gen": { "height": 1160326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfc70ffb97b8f6ea274121ee21e8154f59a600012afee46e25821060d44e0710" } } ], "extra": [ 1, 107, 176, 57, 255, 68, 86, 252, 243, 138, 73, 201, 215, 111, 69, 194, 86, 44, 246, 146, 170, 29, 143, 185, 57, 113, 187, 117, 155, 26, 24, 157, 16, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8