Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4adc29b8aa6985898417f6959f85181a7741014d076e62edfa1579c20f21c47c

Tx prefix hash: 7411e9bea374741c5cc12c28f101ab9f28d8284bee1688b866f0d581295c75d8
Tx public key: cb65b3a83406a974f5b47832c9fe46d5a84ca5d8081d8489c53d8bd4ed4ef47e
Timestamp: 1713434538 Timestamp [UCT]: 2024-04-18 10:02:18 Age [y:d:h:m:s]: 00:355:04:38:44
Block: 1003111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253937 RingCT/type: yes/0
Extra: 01cb65b3a83406a974f5b47832c9fe46d5a84ca5d8081d8489c53d8bd4ed4ef47e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac553f915ca66f5d8276402d5135d96df6aecaa51962869e4b087c99cb5663f2 0.600000000000 1463641 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": 1003121, "vin": [ { "gen": { "height": 1003111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac553f915ca66f5d8276402d5135d96df6aecaa51962869e4b087c99cb5663f2" } } ], "extra": [ 1, 203, 101, 179, 168, 52, 6, 169, 116, 245, 180, 120, 50, 201, 254, 70, 213, 168, 76, 165, 216, 8, 29, 132, 137, 197, 61, 139, 212, 237, 78, 244, 126, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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