Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a08447db2a05363d097931ebf5dc7d3273297f2daac40776064ee84bce7c58c1

Tx prefix hash: 9320f066d8fa495b9774e70321004aa0b8a74d9abfe366a024a97f3f7e59e5b6
Tx public key: c7b8c66ede70eefb22dd8597dc3609bce498c44488c397dbaf3c1eba5ebd4af0
Timestamp: 1724274845 Timestamp [UCT]: 2024-08-21 21:14:05 Age [y:d:h:m:s]: 00:225:18:35:19
Block: 1093003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161226 RingCT/type: yes/0
Extra: 01c7b8c66ede70eefb22dd8597dc3609bce498c44488c397dbaf3c1eba5ebd4af0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e34bc42c19c4c574c628b9d5022142729c485a0fb7358e40e0dd30bad3a653d8 0.600000000000 1567860 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": 1093013, "vin": [ { "gen": { "height": 1093003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e34bc42c19c4c574c628b9d5022142729c485a0fb7358e40e0dd30bad3a653d8" } } ], "extra": [ 1, 199, 184, 198, 110, 222, 112, 238, 251, 34, 221, 133, 151, 220, 54, 9, 188, 228, 152, 196, 68, 136, 195, 151, 219, 175, 60, 30, 186, 94, 189, 74, 240, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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