Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec9996b75a3bdee54a0eda7404053cd01793f56f2238c84a19bef188e3067f6

Tx prefix hash: 6750be6e7d0e510ed204e3b393062d678a400f3ed60f527940b9f1f92c8cf228
Tx public key: bc1c04b960de95a2ff19ffa0826238bdf67dbaf5f37174fa38aa894fcbb1c369
Timestamp: 1694786340 Timestamp [UCT]: 2023-09-15 13:59:00 Age [y:d:h:m:s]: 01:203:02:08:04
Block: 848707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406244 RingCT/type: yes/0
Extra: 01bc1c04b960de95a2ff19ffa0826238bdf67dbaf5f37174fa38aa894fcbb1c3690211000000044b8f5122000000000000000000

1 output(s) for total of 0.945978906000 dcy

stealth address amount amount idx
00: 58973a26fdc2e6e84774bb675d226f957cb61ff3fb26e938199f1f9e13c00c0c 0.945978906000 1302331 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": 848717, "vin": [ { "gen": { "height": 848707 } } ], "vout": [ { "amount": 945978906, "target": { "key": "58973a26fdc2e6e84774bb675d226f957cb61ff3fb26e938199f1f9e13c00c0c" } } ], "extra": [ 1, 188, 28, 4, 185, 96, 222, 149, 162, 255, 25, 255, 160, 130, 98, 56, 189, 246, 125, 186, 245, 243, 113, 116, 250, 56, 170, 137, 79, 203, 177, 195, 105, 2, 17, 0, 0, 0, 4, 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