Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe03e2a955b390515533e939ce4daf687911d787767ce6475318c281fee55f2d

Tx prefix hash: 457e708c4237a57d961ed8a139aca09ce21049258e1b23d7a3d8c5b5e707a95b
Tx public key: 7aec0cf8f1aec968ac314d40a3d4b4c7078b542c70c774105fad30dfd6ec6c0a
Timestamp: 1717044213 Timestamp [UCT]: 2024-05-30 04:43:33 Age [y:d:h:m:s]: 00:363:20:41:08
Block: 1033050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260098 RingCT/type: yes/0
Extra: 017aec0cf8f1aec968ac314d40a3d4b4c7078b542c70c774105fad30dfd6ec6c0a02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9be16814de176bff09b257c6f0ddcfc10be9461015befc576ca7186c7f735170 0.600000000000 1501507 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": 1033060, "vin": [ { "gen": { "height": 1033050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9be16814de176bff09b257c6f0ddcfc10be9461015befc576ca7186c7f735170" } } ], "extra": [ 1, 122, 236, 12, 248, 241, 174, 201, 104, 172, 49, 77, 64, 163, 212, 180, 199, 7, 139, 84, 44, 112, 199, 116, 16, 95, 173, 48, 223, 214, 236, 108, 10, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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