Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ceebe1bb48df8ea8315b3f373e6eb5e9c83f0e3eb61a53dc288b7590035234c

Tx prefix hash: 282d156c91b406e205faaaf61a14b22fa49a9d0dad934840504e7e6ce7991c5e
Tx public key: 442ac640f40e82374795758baddb3f1eedbb41671fde7e21cfd1be02f8e823d5
Timestamp: 1728776155 Timestamp [UCT]: 2024-10-12 23:35:55 Age [y:d:h:m:s]: 00:212:13:27:27
Block: 1130316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151718 RingCT/type: yes/0
Extra: 01442ac640f40e82374795758baddb3f1eedbb41671fde7e21cfd1be02f8e823d502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6af32ad52222c9aa73c25d0e97b40d30bb6d14f926aae48291edbe6d5fa6945 0.600000000000 1613191 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": 1130326, "vin": [ { "gen": { "height": 1130316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6af32ad52222c9aa73c25d0e97b40d30bb6d14f926aae48291edbe6d5fa6945" } } ], "extra": [ 1, 68, 42, 198, 64, 244, 14, 130, 55, 71, 149, 117, 139, 173, 219, 63, 30, 237, 187, 65, 103, 31, 222, 126, 33, 207, 209, 190, 2, 248, 232, 35, 213, 2, 17, 0, 0, 0, 3, 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