Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 968bd163be236e56e34259cb7a9dffc7a4ce33937bcf336b5d474fd62be9b875

Tx prefix hash: 144f67413e3e207be0b47b295e32855971ae1872d1c9b4f33fd02ccd37b98db5
Tx public key: a4820e6e9891c89f51820b78bc6f3fa7f9dd6aa83e29cc44172b91345576742b
Timestamp: 1764352805 Timestamp [UCT]: 2025-11-28 18:00:05 Age [y:d:h:m:s]: 00:007:04:28:12
Block: 1422136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5135 RingCT/type: yes/0
Extra: 01a4820e6e9891c89f51820b78bc6f3fa7f9dd6aa83e29cc44172b91345576742b021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4efebd377345dfa541a8910c39380162389b720dba4c66beccacbbbdf046e6b 0.600000000000 1910701 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": 1422146, "vin": [ { "gen": { "height": 1422136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4efebd377345dfa541a8910c39380162389b720dba4c66beccacbbbdf046e6b" } } ], "extra": [ 1, 164, 130, 14, 110, 152, 145, 200, 159, 81, 130, 11, 120, 188, 111, 63, 167, 249, 221, 106, 168, 62, 41, 204, 68, 23, 43, 145, 52, 85, 118, 116, 43, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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