Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e031547c879839fa9e660f8a6043c2d8f647394ef00a961b58f4ee003e36ec1c

Tx prefix hash: e601cbb2d59b7ffc01ef886e94aab3357593188941a195ec609dfa2a2dbf49aa
Tx public key: 28dfe4fd8a77a7fc6ccce15d3d312018421d01330c74d22463d7e3ab5f8dca0c
Timestamp: 1737596326 Timestamp [UCT]: 2025-01-23 01:38:46 Age [y:d:h:m:s]: 00:146:00:41:08
Block: 1203244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104111 RingCT/type: yes/0
Extra: 0128dfe4fd8a77a7fc6ccce15d3d312018421d01330c74d22463d7e3ab5f8dca0c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8716e2c046285aba86ea804aef65d3940e7d64218ca964d25f8bc3c66d6099f0 0.600000000000 1689917 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": 1203254, "vin": [ { "gen": { "height": 1203244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8716e2c046285aba86ea804aef65d3940e7d64218ca964d25f8bc3c66d6099f0" } } ], "extra": [ 1, 40, 223, 228, 253, 138, 119, 167, 252, 108, 204, 225, 93, 61, 49, 32, 24, 66, 29, 1, 51, 12, 116, 210, 36, 99, 215, 227, 171, 95, 141, 202, 12, 2, 17, 0, 0, 0, 3, 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