Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed8c57802e766a6ed37ea91e38aef4d3ca5d7baac460671938fc416acc2ffa1e

Tx prefix hash: b04924cfc1179ab1d31618e94910ef470fd1c48f12271f9dab9cde9f01883068
Tx public key: 0a5c24256c0d9c97f6b8ba1f344a7f0478424b98f2ac6dda459c94ebbc1431f8
Timestamp: 1737370970 Timestamp [UCT]: 2025-01-20 11:02:50 Age [y:d:h:m:s]: 00:305:12:56:49
Block: 1201370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215924 RingCT/type: yes/0
Extra: 010a5c24256c0d9c97f6b8ba1f344a7f0478424b98f2ac6dda459c94ebbc1431f8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee3504556dfd0090f7221db16b6d81125063afa50b84e761b7d4306c2965e4b9 0.600000000000 1688019 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": 1201380, "vin": [ { "gen": { "height": 1201370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee3504556dfd0090f7221db16b6d81125063afa50b84e761b7d4306c2965e4b9" } } ], "extra": [ 1, 10, 92, 36, 37, 108, 13, 156, 151, 246, 184, 186, 31, 52, 74, 127, 4, 120, 66, 75, 152, 242, 172, 109, 218, 69, 156, 148, 235, 188, 20, 49, 248, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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