Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a09806ee50692de03413e758ccc8d3a428f2fc8456c8527234e593692d858140

Tx prefix hash: 873af45e2a3d65b3144a6b44f477b787621a444444156aeae54d99887b19a151
Tx public key: e81c6aee26234b8e9fb5ee4a2581425d8572b36dbce47da0a397327525d4233a
Timestamp: 1741135802 Timestamp [UCT]: 2025-03-05 00:50:02 Age [y:d:h:m:s]: 00:095:07:28:36
Block: 1232318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68187 RingCT/type: yes/0
Extra: 01e81c6aee26234b8e9fb5ee4a2581425d8572b36dbce47da0a397327525d4233a0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 416f05f0ef7af502553b6c00c937f6cae683b006006df31f4b20642e9a615ef9 0.600000000000 1719231 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": 1232328, "vin": [ { "gen": { "height": 1232318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "416f05f0ef7af502553b6c00c937f6cae683b006006df31f4b20642e9a615ef9" } } ], "extra": [ 1, 232, 28, 106, 238, 38, 35, 75, 142, 159, 181, 238, 74, 37, 129, 66, 93, 133, 114, 179, 109, 188, 228, 125, 160, 163, 151, 50, 117, 37, 212, 35, 58, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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