Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a43bffa59425c7967e06b89a2470ac88e14c09b36a1273e7aa4eb86f459c1a

Tx prefix hash: 189e8b3a9ad298eac6a8dc909385832a558b6823c758cba04e9d6ff50ce20b77
Tx public key: 445cb6ed2f9eb515290089e78a7e1331f8b4aac26c115bafa4702c4d2c7fff83
Timestamp: 1713359104 Timestamp [UCT]: 2024-04-17 13:05:04 Age [y:d:h:m:s]: 00:357:10:20:45
Block: 1002497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255524 RingCT/type: yes/0
Extra: 01445cb6ed2f9eb515290089e78a7e1331f8b4aac26c115bafa4702c4d2c7fff8302110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55cade2b0cf0ac3d229279460057c332808b1ef28557ff7e0540a2a5e9ea7428 0.600000000000 1463013 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": 1002507, "vin": [ { "gen": { "height": 1002497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55cade2b0cf0ac3d229279460057c332808b1ef28557ff7e0540a2a5e9ea7428" } } ], "extra": [ 1, 68, 92, 182, 237, 47, 158, 181, 21, 41, 0, 137, 231, 138, 126, 19, 49, 248, 180, 170, 194, 108, 17, 91, 175, 164, 112, 44, 77, 44, 127, 255, 131, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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