Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6932d66c8c96cf4fcf4b80e99a8bc38238e9d46544ea72d6ed99f6c4f0259688

Tx prefix hash: ef3a3c6ee394139d845797084f2eda8f193da4313589fc7298a55b1df36c706f
Tx public key: 60fb913cc304578cc0b9a081f1838b4909be5e81e62e058cdec048238dcf6db8
Timestamp: 1726222380 Timestamp [UCT]: 2024-09-13 10:13:00 Age [y:d:h:m:s]: 00:203:21:59:14
Block: 1109142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145574 RingCT/type: yes/0
Extra: 0160fb913cc304578cc0b9a081f1838b4909be5e81e62e058cdec048238dcf6db802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53628a0d5bd3c126b520fb6db3b8a4b3e63efd8fff49359970459e830c8aad1e 0.600000000000 1587287 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": 1109152, "vin": [ { "gen": { "height": 1109142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53628a0d5bd3c126b520fb6db3b8a4b3e63efd8fff49359970459e830c8aad1e" } } ], "extra": [ 1, 96, 251, 145, 60, 195, 4, 87, 140, 192, 185, 160, 129, 241, 131, 139, 73, 9, 190, 94, 129, 230, 46, 5, 140, 222, 192, 72, 35, 141, 207, 109, 184, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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