Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40dced8b472cd6d11a0c5e81a013f26166b177fba3d187d7d3c6281d6507fc91

Tx prefix hash: 479660ce4e67a9a2413337a42a5ebca106af182690c62f3f69a2a2406bc96e6c
Tx public key: c6b9e25029b9ddcb1d33254ad0edb34551c371710fc9fc038910d918c6469d8d
Timestamp: 1729572666 Timestamp [UCT]: 2024-10-22 04:51:06 Age [y:d:h:m:s]: 00:000:10:33:11
Block: 1136875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322 RingCT/type: yes/0
Extra: 01c6b9e25029b9ddcb1d33254ad0edb34551c371710fc9fc038910d918c6469d8d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbbc4806fe3033cdee6f09b95e10eb27f41a417c5d5cb31315f4338c6eac8e49 0.600000000000 1620264 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": 1136885, "vin": [ { "gen": { "height": 1136875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbbc4806fe3033cdee6f09b95e10eb27f41a417c5d5cb31315f4338c6eac8e49" } } ], "extra": [ 1, 198, 185, 226, 80, 41, 185, 221, 203, 29, 51, 37, 74, 208, 237, 179, 69, 81, 195, 113, 113, 15, 201, 252, 3, 137, 16, 217, 24, 198, 70, 157, 141, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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