Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 804d3d01e848c2fb97642d04e672ce5641e57271229685676f8114aae41eea25

Tx prefix hash: bc7f9e174b5a6351b54c8d422106aa83c066c930209d59ddc12ee61f2fd540e4
Tx public key: 7cd4fd60a72a54cadb1c82fe65e6aa110c4ce175cf8346dbd16085c552914ec5
Timestamp: 1695224688 Timestamp [UCT]: 2023-09-20 15:44:48 Age [y:d:h:m:s]: 01:184:21:00:40
Block: 852344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393212 RingCT/type: yes/0
Extra: 017cd4fd60a72a54cadb1c82fe65e6aa110c4ce175cf8346dbd16085c552914ec502110000001c4b8f5122000000000000000000

1 output(s) for total of 0.920090521000 dcy

stealth address amount amount idx
00: ab234c694981df419894e4043a61d8bb734f1fce6df04f370dd8969d5438636d 0.920090521000 1306176 of 0

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": 852354, "vin": [ { "gen": { "height": 852344 } } ], "vout": [ { "amount": 920090521, "target": { "key": "ab234c694981df419894e4043a61d8bb734f1fce6df04f370dd8969d5438636d" } } ], "extra": [ 1, 124, 212, 253, 96, 167, 42, 84, 202, 219, 28, 130, 254, 101, 230, 170, 17, 12, 76, 225, 117, 207, 131, 70, 219, 209, 96, 133, 197, 82, 145, 78, 197, 2, 17, 0, 0, 0, 28, 75, 143, 81, 34, 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