Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010b7b0773a47a5c29363c8a9b39d0f1fe46178bf1afd79b76fbf00941c2e615

Tx prefix hash: fd20692a4ec507d845857d41c4a671d25f5cfecdb71c99c7ebaefa77b7bc7d89
Tx public key: 5e39449cf09c3f8fcd75417b40ff0b5459c966e1c41cde0dfd869884c92b78e7
Timestamp: 1745614825 Timestamp [UCT]: 2025-04-25 21:00:25 Age [y:d:h:m:s]: 00:242:11:50:29
Block: 1269401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171058 RingCT/type: yes/0
Extra: 015e39449cf09c3f8fcd75417b40ff0b5459c966e1c41cde0dfd869884c92b78e70211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee0ae2071d64692293a19646eaacb4053b639b44304b8e62ae8084253ba9498e 0.600000000000 1756636 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": 1269411, "vin": [ { "gen": { "height": 1269401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee0ae2071d64692293a19646eaacb4053b639b44304b8e62ae8084253ba9498e" } } ], "extra": [ 1, 94, 57, 68, 156, 240, 156, 63, 143, 205, 117, 65, 123, 64, 255, 11, 84, 89, 201, 102, 225, 196, 28, 222, 13, 253, 134, 152, 132, 201, 43, 120, 231, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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