Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69583f480881eee609c407f20e21c6d2b86169504dc020a644d5fd94193a5402

Tx prefix hash: 9965aaad6b03b8d91e3df5fb49cc0d3a0e618431474bb96200b663167195eed6
Tx public key: dc8b99f542eafd7aedfb602f225e110379dd9a57fe9a41fd0c0df3122601bcb2
Timestamp: 1701434810 Timestamp [UCT]: 2023-12-01 12:46:50 Age [y:d:h:m:s]: 01:187:13:03:10
Block: 903635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395238 RingCT/type: yes/0
Extra: 01dc8b99f542eafd7aedfb602f225e110379dd9a57fe9a41fd0c0df3122601bcb202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.622131378000 dcy

stealth address amount amount idx
00: 3f2b305b5d8e6c2397dc7bdcc3dbe3a349df8cb626116c7444f5fe671f8fc7b4 0.622131378000 1360320 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": 903645, "vin": [ { "gen": { "height": 903635 } } ], "vout": [ { "amount": 622131378, "target": { "key": "3f2b305b5d8e6c2397dc7bdcc3dbe3a349df8cb626116c7444f5fe671f8fc7b4" } } ], "extra": [ 1, 220, 139, 153, 245, 66, 234, 253, 122, 237, 251, 96, 47, 34, 94, 17, 3, 121, 221, 154, 87, 254, 154, 65, 253, 12, 13, 243, 18, 38, 1, 188, 178, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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