Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a8ef51496d74ddf6681bfdcd2b48212068919204b6d2d2719f01da85e7516e

Tx prefix hash: c2a4aea442234bd17689b63524d7b67d49607d2e26aa7342d75fdc7f09ffd8a8
Tx public key: ffe84a3f69e4ba3c95b026b9a30335ee778c03a0d7882e229accdfbe2643f3f0
Timestamp: 1688261747 Timestamp [UCT]: 2023-07-02 01:35:47 Age [y:d:h:m:s]: 01:200:17:45:20
Block: 794689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404834 RingCT/type: yes/0
Extra: 01ffe84a3f69e4ba3c95b026b9a30335ee778c03a0d7882e229accdfbe2643f3f0021100000001faf35c9c000000000000000000

1 output(s) for total of 1.428451796000 dcy

stealth address amount amount idx
00: 8ad2dede5277a22d7313599f19844e72ce33dad9aa219dd9c1008e233f53db81 1.428451796000 1245456 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": 794699, "vin": [ { "gen": { "height": 794689 } } ], "vout": [ { "amount": 1428451796, "target": { "key": "8ad2dede5277a22d7313599f19844e72ce33dad9aa219dd9c1008e233f53db81" } } ], "extra": [ 1, 255, 232, 74, 63, 105, 228, 186, 60, 149, 176, 38, 185, 163, 3, 53, 238, 119, 140, 3, 160, 215, 136, 46, 34, 154, 204, 223, 190, 38, 67, 243, 240, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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