Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a18f4c307f3e670ba9e2cb172f178127882cd47dfe8745c06de9d12e10e1a173

Tx prefix hash: 55776f34387ae5daef4f8108d3ddcdf4232e3706bc4725be1fe0df0fa3e673bb
Tx public key: 49c1d7038158278a7d1f8a3e84a815910df8165c766b5c8d6ab3b36c298a9309
Timestamp: 1742623220 Timestamp [UCT]: 2025-03-22 06:00:20 Age [y:d:h:m:s]: 00:048:00:56:17
Block: 1244635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34352 RingCT/type: yes/0
Extra: 0149c1d7038158278a7d1f8a3e84a815910df8165c766b5c8d6ab3b36c298a9309021100000001af845649000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99662528f71ed1ae4d4884e51442644d4f755d9ebde425de2a5cdfaab3176e8e 0.600000000000 1731626 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": 1244645, "vin": [ { "gen": { "height": 1244635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99662528f71ed1ae4d4884e51442644d4f755d9ebde425de2a5cdfaab3176e8e" } } ], "extra": [ 1, 73, 193, 215, 3, 129, 88, 39, 138, 125, 31, 138, 62, 132, 168, 21, 145, 13, 248, 22, 92, 118, 107, 92, 141, 106, 179, 179, 108, 41, 138, 147, 9, 2, 17, 0, 0, 0, 1, 175, 132, 86, 73, 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