Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6c6414450c4dde99c2d002539a959c7544d3c83e478194aec2c103dbfd3302

Tx prefix hash: 9456cef8e4772cdd457d364cb5cc2b31c7382664bd3080be158c70293615c815
Tx public key: 248309114418200928d3d6e3f72d76c0c1e00f5c5ef528101ed89f12ffc470a8
Timestamp: 1717017760 Timestamp [UCT]: 2024-05-29 21:22:40 Age [y:d:h:m:s]: 01:187:23:01:26
Block: 1032833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392966 RingCT/type: yes/0
Extra: 01248309114418200928d3d6e3f72d76c0c1e00f5c5ef528101ed89f12ffc470a802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac183eabac62f74a2df30ea1077e0ba1a1e59a790e8043e82862463f882bff0 0.600000000000 1501288 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": 1032843, "vin": [ { "gen": { "height": 1032833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac183eabac62f74a2df30ea1077e0ba1a1e59a790e8043e82862463f882bff0" } } ], "extra": [ 1, 36, 131, 9, 17, 68, 24, 32, 9, 40, 211, 214, 227, 247, 45, 118, 192, 193, 224, 15, 92, 94, 245, 40, 16, 30, 216, 159, 18, 255, 196, 112, 168, 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