Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae0a19bf6e604be7165da0236229164d62c8edd36e57f9dd44cc70e67496ab2

Tx prefix hash: bd46f0876e99667894a4e1f4b703dd8e617c40aa302f20ef8ae13edfae98224c
Tx public key: 4af3bad6c413d4bf217269a5c308028f4ab0feae8919f76cdcf88b42e080b045
Timestamp: 1761398996 Timestamp [UCT]: 2025-10-25 13:29:56 Age [y:d:h:m:s]: 00:033:16:25:27
Block: 1397660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24112 RingCT/type: yes/0
Extra: 014af3bad6c413d4bf217269a5c308028f4ab0feae8919f76cdcf88b42e080b0450211000000075dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5d022ce3d5d90064e44e7a6cf9c2ede0de1708a67c79fff5cada10a65375d25 0.600000000000 1885951 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": 1397670, "vin": [ { "gen": { "height": 1397660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5d022ce3d5d90064e44e7a6cf9c2ede0de1708a67c79fff5cada10a65375d25" } } ], "extra": [ 1, 74, 243, 186, 214, 196, 19, 212, 191, 33, 114, 105, 165, 195, 8, 2, 143, 74, 176, 254, 174, 137, 25, 247, 108, 220, 248, 139, 66, 224, 128, 176, 69, 2, 17, 0, 0, 0, 7, 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