Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3671c4869719fa18aaf976e61addf94d7a47b2bc1ca92fbe25fbdea518aa2c16

Tx prefix hash: c84dcf763a7a05b57195e0f65cdad2bda2bcd653734905768325ef74fb7b8b7e
Tx public key: dc499627605273e01c7dcd157ebf9a21baf187f4d23de1fc7aefefaa2bf477fd
Timestamp: 1749560209 Timestamp [UCT]: 2025-06-10 12:56:49 Age [y:d:h:m:s]: 00:151:14:56:18
Block: 1302066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106042 RingCT/type: yes/0
Extra: 01dc499627605273e01c7dcd157ebf9a21baf187f4d23de1fc7aefefaa2bf477fd02110000000dbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2146b876dcfb06b99e9544c459d7b881ca7ff4e898446cdb59f907ef6b7fadd 0.600000000000 1789635 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": 1302076, "vin": [ { "gen": { "height": 1302066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2146b876dcfb06b99e9544c459d7b881ca7ff4e898446cdb59f907ef6b7fadd" } } ], "extra": [ 1, 220, 73, 150, 39, 96, 82, 115, 224, 28, 125, 205, 21, 126, 191, 154, 33, 186, 241, 135, 244, 210, 61, 225, 252, 122, 239, 239, 170, 43, 244, 119, 253, 2, 17, 0, 0, 0, 13, 191, 81, 178, 162, 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