Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c57597c8d5a39a2d318933c5e708d49645ef092eb8c96ef2bb8ec9eedcd62cf4

Tx prefix hash: cc02c50831638956effc14f7cf07f8ae7731bcbeff22f1250b5efc0e5ead24a6
Tx public key: 103338158a7e0cba3cf6a0ea27c2558fa13e367432ef3e59d69cf3df2cba6f1e
Timestamp: 1704671174 Timestamp [UCT]: 2024-01-07 23:46:14 Age [y:d:h:m:s]: 01:080:22:32:27
Block: 930459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318949 RingCT/type: yes/0
Extra: 01103338158a7e0cba3cf6a0ea27c2558fa13e367432ef3e59d69cf3df2cba6f1e02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b8753c0f9253e5701aa9554773975d841299831b21b1bb64cb00e22cbc5dba 0.600000000000 1388341 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": 930469, "vin": [ { "gen": { "height": 930459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b8753c0f9253e5701aa9554773975d841299831b21b1bb64cb00e22cbc5dba" } } ], "extra": [ 1, 16, 51, 56, 21, 138, 126, 12, 186, 60, 246, 160, 234, 39, 194, 85, 143, 161, 62, 54, 116, 50, 239, 62, 89, 214, 156, 243, 223, 44, 186, 111, 30, 2, 17, 0, 0, 0, 5, 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