Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2345d24924fdb3cf3773c84e41d29aef267bf8213f697965fe129d7bc63cfa42

Tx prefix hash: 74694c366e0e2a0d3cbf83a76befb3685bd6752cf2f9533ad19cde8f021fd39f
Tx public key: c2de1ac1b260d6a9b941626cc2eb954fc400b759c34d2d6170559861c0ad4da9
Timestamp: 1710603141 Timestamp [UCT]: 2024-03-16 15:32:21 Age [y:d:h:m:s]: 00:188:23:20:16
Block: 979667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135354 RingCT/type: yes/0
Extra: 01c2de1ac1b260d6a9b941626cc2eb954fc400b759c34d2d6170559861c0ad4da90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62e8bf7897397c3bcae6eb0e47db556888c08b3091ea8439b8d95751471fa4f8 0.600000000000 1439718 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": 979677, "vin": [ { "gen": { "height": 979667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62e8bf7897397c3bcae6eb0e47db556888c08b3091ea8439b8d95751471fa4f8" } } ], "extra": [ 1, 194, 222, 26, 193, 178, 96, 214, 169, 185, 65, 98, 108, 194, 235, 149, 79, 196, 0, 183, 89, 195, 77, 45, 97, 112, 85, 152, 97, 192, 173, 77, 169, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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