Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6077d61f34fbee4603f55f7d7b3c7a469946ba8514cfbd4093638d55157c0e04

Tx prefix hash: d250d2a704d18585384b4977837e126fc0a2671740e75715134fda850abc2ec3
Tx public key: bed1baacd8b8c0dea4647d6847a39ea0bf1cc7efc1223b3dea5ef02ff6ce17f1
Timestamp: 1647639903 Timestamp [UCT]: 2022-03-18 21:45:03 Age [y:d:h:m:s]: 02:280:02:24:58
Block: 461378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719722 RingCT/type: yes/0
Extra: 01bed1baacd8b8c0dea4647d6847a39ea0bf1cc7efc1223b3dea5ef02ff6ce17f10211000000035eb576c5000000000000000000

1 output(s) for total of 18.166171964000 dcy

stealth address amount amount idx
00: af2e3025f41605952844a8d5e7a3e7050b9872a4ee49ef0137b30eefa2b140f6 18.166171964000 878603 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": 461388, "vin": [ { "gen": { "height": 461378 } } ], "vout": [ { "amount": 18166171964, "target": { "key": "af2e3025f41605952844a8d5e7a3e7050b9872a4ee49ef0137b30eefa2b140f6" } } ], "extra": [ 1, 190, 209, 186, 172, 216, 184, 192, 222, 164, 100, 125, 104, 71, 163, 158, 160, 191, 28, 199, 239, 193, 34, 59, 61, 234, 94, 240, 47, 246, 206, 23, 241, 2, 17, 0, 0, 0, 3, 94, 181, 118, 197, 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