Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f8b1d97ef5e86d93acd9a06715189dbeb0db3e6870b602273e48dd40e9fc13b

Tx prefix hash: 100e7825c37f3103bc10ff5aef9936bc1f9f8ded373e52c04598401621531533
Tx public key: 12864f078e08e3894dc5c8f8f5b1fbdf8ea7bb1bb3b247070224d920c680abbf
Timestamp: 1713812368 Timestamp [UCT]: 2024-04-22 18:59:28 Age [y:d:h:m:s]: 01:000:13:26:08
Block: 1006257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261335 RingCT/type: yes/0
Extra: 0112864f078e08e3894dc5c8f8f5b1fbdf8ea7bb1bb3b247070224d920c680abbf02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e367d2f8e9ae58da1087eb505571a18d18582781381008da8d8eed3908b59a6 0.600000000000 1467219 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": 1006267, "vin": [ { "gen": { "height": 1006257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e367d2f8e9ae58da1087eb505571a18d18582781381008da8d8eed3908b59a6" } } ], "extra": [ 1, 18, 134, 79, 7, 142, 8, 227, 137, 77, 197, 200, 248, 245, 177, 251, 223, 142, 167, 187, 27, 179, 178, 71, 7, 2, 36, 217, 32, 198, 128, 171, 191, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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