Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d80605a616c1905a6b4226b2c70c49835c18d3d26fd790feb235db393cb7983

Tx prefix hash: ba3c31e311c2b1086788ef95aaed2c510a3821c3a9cf416637c533d34379d993
Tx public key: 7232e0ea26e178fdde0c2eca4c43aaa410e799900fba13c03b82503f294ecdf7
Timestamp: 1720133733 Timestamp [UCT]: 2024-07-04 22:55:33 Age [y:d:h:m:s]: 01:127:04:31:48
Block: 1058656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349437 RingCT/type: yes/0
Extra: 017232e0ea26e178fdde0c2eca4c43aaa410e799900fba13c03b82503f294ecdf702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42c4277de2e096a974c80bf8a3d794080f13ca3148e7380d6700c9b31f519891 0.600000000000 1529113 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": 1058666, "vin": [ { "gen": { "height": 1058656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42c4277de2e096a974c80bf8a3d794080f13ca3148e7380d6700c9b31f519891" } } ], "extra": [ 1, 114, 50, 224, 234, 38, 225, 120, 253, 222, 12, 46, 202, 76, 67, 170, 164, 16, 231, 153, 144, 15, 186, 19, 192, 59, 130, 80, 63, 41, 78, 205, 247, 2, 17, 0, 0, 0, 2, 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