Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 524ed00549ec659cb5b6ca7397a3455fb3f2d86433cee85128be55b9fb2ffeac

Tx prefix hash: fa589493be671b4975fca630f4d405b91b481fcd5853cb687d686eaf0c8f8de0
Tx public key: 415c36b18ab8cbdf819bdae765d19d18bb6603ba7f9059ccfb3bfc0d8a1586f6
Timestamp: 1752049902 Timestamp [UCT]: 2025-07-09 08:31:42 Age [y:d:h:m:s]: 00:175:08:14:32
Block: 1321834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123890 RingCT/type: yes/0
Extra: 01415c36b18ab8cbdf819bdae765d19d18bb6603ba7f9059ccfb3bfc0d8a1586f602110000000f43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a24100ef7e98caec06d79c69114ace0b819a46a8f0fa9f18a51a570e927b87 0.600000000000 1809543 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": 1321844, "vin": [ { "gen": { "height": 1321834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a24100ef7e98caec06d79c69114ace0b819a46a8f0fa9f18a51a570e927b87" } } ], "extra": [ 1, 65, 92, 54, 177, 138, 184, 203, 223, 129, 155, 218, 231, 101, 209, 157, 24, 187, 102, 3, 186, 127, 144, 89, 204, 251, 59, 252, 13, 138, 21, 134, 246, 2, 17, 0, 0, 0, 15, 67, 132, 109, 102, 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