Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc511d61f5e70441d3bef71ba588f9cbeb599c796420eb595e5689e1329b65c

Tx prefix hash: 6ea0416c68cd33aff28e16e8052553c7f6b7b046e96db064a25b2cf695e4444f
Tx public key: bcb3810f881d4e21063561f0a27bf9bf25a616cec566936d22b598f67f8808f6
Timestamp: 1744034330 Timestamp [UCT]: 2025-04-07 13:58:50 Age [y:d:h:m:s]: 00:036:17:42:05
Block: 1256303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26294 RingCT/type: yes/0
Extra: 01bcb3810f881d4e21063561f0a27bf9bf25a616cec566936d22b598f67f8808f6021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 211c204f78d314fc65aadc06abf4da85f287e052f49d287509f6e4222fb6d8cb 0.600000000000 1743416 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": 1256313, "vin": [ { "gen": { "height": 1256303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "211c204f78d314fc65aadc06abf4da85f287e052f49d287509f6e4222fb6d8cb" } } ], "extra": [ 1, 188, 179, 129, 15, 136, 29, 78, 33, 6, 53, 97, 240, 162, 123, 249, 191, 37, 166, 22, 206, 197, 102, 147, 109, 34, 181, 152, 246, 127, 136, 8, 246, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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