Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ababefc679fca0ed4d38700d83e1b8becc3caf8faa070ddbd94c172a90551b3

Tx prefix hash: a269d707f3a5d467a03c14548f0529e33a32aad58f3d335bafbf8f8db1d04fe6
Tx public key: 320f019c3a619550c8135649f3e6985e3465173f39f13d1cf8e6d73cb95f536f
Timestamp: 1736326290 Timestamp [UCT]: 2025-01-08 08:51:30 Age [y:d:h:m:s]: 00:091:19:36:19
Block: 1192768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65408 RingCT/type: yes/0
Extra: 01320f019c3a619550c8135649f3e6985e3465173f39f13d1cf8e6d73cb95f536f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7af852ffb069fc9d9e7d4b47ec8dce495382e9b5f5dff1028ff21901031715b8 0.600000000000 1679325 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": 1192778, "vin": [ { "gen": { "height": 1192768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7af852ffb069fc9d9e7d4b47ec8dce495382e9b5f5dff1028ff21901031715b8" } } ], "extra": [ 1, 50, 15, 1, 156, 58, 97, 149, 80, 200, 19, 86, 73, 243, 230, 152, 94, 52, 101, 23, 63, 57, 241, 61, 28, 248, 230, 215, 60, 185, 95, 83, 111, 2, 17, 0, 0, 0, 1, 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