Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a5d4c4f15fea369c40dae7559b79eea118206c590bf90da5633ce43183c724

Tx prefix hash: 491852e26325183b9b66beaecbb3f9c531f6c32600f4748114d4607bb99c445e
Tx public key: bdee521a2c5b0b773b1b9149f1983f35b2a49b9cf626af0ad3f9ad04a72c1dfb
Timestamp: 1694037630 Timestamp [UCT]: 2023-09-06 22:00:30 Age [y:d:h:m:s]: 02:062:22:49:37
Block: 842497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564684 RingCT/type: yes/0
Extra: 01bdee521a2c5b0b773b1b9149f1983f35b2a49b9cf626af0ad3f9ad04a72c1dfb02110000000333af99f4000000000000000000

1 output(s) for total of 0.991906885000 dcy

stealth address amount amount idx
00: 60ac5a9399a9958fc646ff450dcf803b6a99d49b0a26b2446d33c0b75b32940f 0.991906885000 1295621 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": 842507, "vin": [ { "gen": { "height": 842497 } } ], "vout": [ { "amount": 991906885, "target": { "key": "60ac5a9399a9958fc646ff450dcf803b6a99d49b0a26b2446d33c0b75b32940f" } } ], "extra": [ 1, 189, 238, 82, 26, 44, 91, 11, 119, 59, 27, 145, 73, 241, 152, 63, 53, 178, 164, 155, 156, 246, 38, 175, 10, 211, 249, 173, 4, 167, 44, 29, 251, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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