Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6275e27f8c6cba32e42b792d97882253093f591e98ab1c6387bccd9e514e3e6

Tx prefix hash: fcadaa49108601a122dcad5780373a04886f07fe1af2f8a0eecb64d8af7a4cd2
Tx public key: d3d247940681fe9410b8cca22df4b1f85495fd3ba948b029590fa3cbeec983a5
Timestamp: 1706638002 Timestamp [UCT]: 2024-01-30 18:06:42 Age [y:d:h:m:s]: 01:058:20:51:54
Block: 946753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303156 RingCT/type: yes/0
Extra: 01d3d247940681fe9410b8cca22df4b1f85495fd3ba948b029590fa3cbeec983a5021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86be8af4e32c90c5eec1593fc33e2e68e50f7d7935001c2f4ceb085b5191a13b 0.600000000000 1405093 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": 946763, "vin": [ { "gen": { "height": 946753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86be8af4e32c90c5eec1593fc33e2e68e50f7d7935001c2f4ceb085b5191a13b" } } ], "extra": [ 1, 211, 210, 71, 148, 6, 129, 254, 148, 16, 184, 204, 162, 45, 244, 177, 248, 84, 149, 253, 59, 169, 72, 176, 41, 89, 15, 163, 203, 238, 201, 131, 165, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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