Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54cf701c99e4860daaa64c7960d8a81230dc2783b506efef078639c0ce1892cd

Tx prefix hash: 0735c34a3dad197aff18b73f7a4d0d76b1456d392fd03f5b3a3c55a72f24f24f
Tx public key: ba7e589521479ecae227b1df3a4976d9274d9883b2ca91acd8a72b8877bb68af
Timestamp: 1702310400 Timestamp [UCT]: 2023-12-11 16:00:00 Age [y:d:h:m:s]: 01:097:21:30:30
Block: 910901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331116 RingCT/type: yes/0
Extra: 01ba7e589521479ecae227b1df3a4976d9274d9883b2ca91acd8a72b8877bb68af02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 026725b44c7c24db474e007d97868b5fe6f9cb1128bddc0debde37a72369a317 0.600000000000 1368076 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": 910911, "vin": [ { "gen": { "height": 910901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "026725b44c7c24db474e007d97868b5fe6f9cb1128bddc0debde37a72369a317" } } ], "extra": [ 1, 186, 126, 88, 149, 33, 71, 158, 202, 226, 39, 177, 223, 58, 73, 118, 217, 39, 77, 152, 131, 178, 202, 145, 172, 216, 167, 43, 136, 119, 187, 104, 175, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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