Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3969bbd9af5b646d382be1c65d7b978a1146969f773a0241958eead47c0c86db

Tx prefix hash: 790c2f89e5591cb4648f9c3eb4af298eb252c64b446aa776bd3280a3574eb3a0
Tx public key: 272d4a36a1487a6be4af5dc22d05bddbe946848a79e4f13a3aec56865b87b346
Timestamp: 1761279572 Timestamp [UCT]: 2025-10-24 04:19:32 Age [y:d:h:m:s]: 00:016:17:44:55
Block: 1396682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11975 RingCT/type: yes/0
Extra: 01272d4a36a1487a6be4af5dc22d05bddbe946848a79e4f13a3aec56865b87b3460211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2167de48da637b67fbf4fa1a35cfb4e9fd40e91c28d83587d7c2b30c737bdd12 0.600000000000 1884969 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": 1396692, "vin": [ { "gen": { "height": 1396682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2167de48da637b67fbf4fa1a35cfb4e9fd40e91c28d83587d7c2b30c737bdd12" } } ], "extra": [ 1, 39, 45, 74, 54, 161, 72, 122, 107, 228, 175, 93, 194, 45, 5, 189, 219, 233, 70, 132, 138, 121, 228, 241, 58, 58, 236, 86, 134, 91, 135, 179, 70, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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