Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7843c8bf7930b2f7ad6bd978d5d7e8499212cbf745787f5570d3df40a381b59

Tx prefix hash: 013fc6f0d6d4d40a3d3d5dbe61e98896619d5951373a4b0171d51313362173a7
Tx public key: 9bb141a785cc77c0e33931337edf0be92f2986de61a1da66d1cb6a7d172d3bfc
Timestamp: 1736353277 Timestamp [UCT]: 2025-01-08 16:21:17 Age [y:d:h:m:s]: 00:157:20:39:10
Block: 1192992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112550 RingCT/type: yes/0
Extra: 019bb141a785cc77c0e33931337edf0be92f2986de61a1da66d1cb6a7d172d3bfc021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0673c4b020c988d6b1a70fe5aa43ca7f66d6555808721ff89e22ed82a94fb14d 0.600000000000 1679549 of 15

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": 1193002, "vin": [ { "gen": { "height": 1192992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0673c4b020c988d6b1a70fe5aa43ca7f66d6555808721ff89e22ed82a94fb14d" } } ], "extra": [ 1, 155, 177, 65, 167, 133, 204, 119, 192, 227, 57, 49, 51, 126, 223, 11, 233, 47, 41, 134, 222, 97, 161, 218, 102, 209, 203, 106, 125, 23, 45, 59, 252, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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