Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93dfd3c9955fdc7d8b5c45414984239529c387b63e41b8357a46f31704be6e5a

Tx prefix hash: cbe3aa9716c399b4f5a92171a79e020ed3e1ec05927dcf32948fd4de4dab82b7
Tx public key: a58be1decb58ef18ee8b81e200ef1a6cfc1257b9ef833a23e65e69e5fcc07ba4
Timestamp: 1737734831 Timestamp [UCT]: 2025-01-24 16:07:11 Age [y:d:h:m:s]: 00:146:04:38:32
Block: 1204382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104213 RingCT/type: yes/0
Extra: 01a58be1decb58ef18ee8b81e200ef1a6cfc1257b9ef833a23e65e69e5fcc07ba402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae4995f94c70497206d9af41582b0cb9a842410168cc622caea7551a00ee1af3 0.600000000000 1691067 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": 1204392, "vin": [ { "gen": { "height": 1204382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae4995f94c70497206d9af41582b0cb9a842410168cc622caea7551a00ee1af3" } } ], "extra": [ 1, 165, 139, 225, 222, 203, 88, 239, 24, 238, 139, 129, 226, 0, 239, 26, 108, 252, 18, 87, 185, 239, 131, 58, 35, 230, 94, 105, 229, 252, 192, 123, 164, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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