Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a81d6f70c09c8060eeacb8400a2c3a435f50d4e580eb68d332f4d73b214b71e

Tx prefix hash: 5ff3ce0cfc6daca7524f952c4a780dec9ef50bca75a67c562341230b419ac152
Tx public key: 67a330d1e5416a062f832e64c29f5540b07a63618f391a8419d77e0b73b749ae
Timestamp: 1732569112 Timestamp [UCT]: 2024-11-25 21:11:52 Age [y:d:h:m:s]: 00:129:01:07:19
Block: 1161661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92024 RingCT/type: yes/0
Extra: 0167a330d1e5416a062f832e64c29f5540b07a63618f391a8419d77e0b73b749ae021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2cf221a9b105ba7028e0c295e797824ae25177169c3161386dc3b80adee2b89 0.600000000000 1647316 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": 1161671, "vin": [ { "gen": { "height": 1161661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2cf221a9b105ba7028e0c295e797824ae25177169c3161386dc3b80adee2b89" } } ], "extra": [ 1, 103, 163, 48, 209, 229, 65, 106, 6, 47, 131, 46, 100, 194, 159, 85, 64, 176, 122, 99, 97, 143, 57, 26, 132, 25, 215, 126, 11, 115, 183, 73, 174, 2, 17, 0, 0, 0, 1, 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