Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a055547640c39ee1906f40992c7db75e68f3a3512c7e9318829e07496fe4aa65

Tx prefix hash: 63a3bac56d8c5b5aa47c416674227c0dfce6a7073edc60a4b1c28e6722eb5e5b
Tx public key: a2c862726a28a790a0e1c5ee41bbf28b41afb3aaf16eea6b6e6ab95d42444bdf
Timestamp: 1697644648 Timestamp [UCT]: 2023-10-18 15:57:28 Age [y:d:h:m:s]: 01:179:13:59:01
Block: 872426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389371 RingCT/type: yes/0
Extra: 01a2c862726a28a790a0e1c5ee41bbf28b41afb3aaf16eea6b6e6ab95d42444bdf02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.789388008000 dcy

stealth address amount amount idx
00: 51ab4af805a258928864d1dcc3c405d8e478b44cba2169c8df87c2ae39957310 0.789388008000 1327514 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": 872436, "vin": [ { "gen": { "height": 872426 } } ], "vout": [ { "amount": 789388008, "target": { "key": "51ab4af805a258928864d1dcc3c405d8e478b44cba2169c8df87c2ae39957310" } } ], "extra": [ 1, 162, 200, 98, 114, 106, 40, 167, 144, 160, 225, 197, 238, 65, 187, 242, 139, 65, 175, 179, 170, 241, 110, 234, 107, 110, 106, 185, 93, 66, 68, 75, 223, 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