Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: debd16c9a9b1d09937f22f57c8da10c7e1a4d2d94d83c6e4976c8720fd5adf23

Tx prefix hash: 78727ce838ef0ae8c3b8b67c9c377f32aa1d572490d4978f0c7fb933e7ec5dc1
Tx public key: 73a30db2a0fd2aa16dfba6b2f85149e36f138474048f562385141b28ced2690a
Timestamp: 1677903515 Timestamp [UCT]: 2023-03-04 04:18:35 Age [y:d:h:m:s]: 01:360:02:35:53
Block: 709436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518038 RingCT/type: yes/0
Extra: 0173a30db2a0fd2aa16dfba6b2f85149e36f138474048f562385141b28ced2690a0211000000015029cbac000000000000000000

1 output(s) for total of 2.737435724000 dcy

stealth address amount amount idx
00: ea387e8cefddab8bc603e7270aae8e098aaa7f098c0b6e87fc6e359215f9dbab 2.737435724000 1153421 of 0

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": 709446, "vin": [ { "gen": { "height": 709436 } } ], "vout": [ { "amount": 2737435724, "target": { "key": "ea387e8cefddab8bc603e7270aae8e098aaa7f098c0b6e87fc6e359215f9dbab" } } ], "extra": [ 1, 115, 163, 13, 178, 160, 253, 42, 161, 109, 251, 166, 178, 248, 81, 73, 227, 111, 19, 132, 116, 4, 143, 86, 35, 133, 20, 27, 40, 206, 210, 105, 10, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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