Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b2932459c5631079c526c3bb4f291ecf274fff07b41472b21f06ea67d9d2914

Tx prefix hash: 24b3a1ef35478c00f75afcec07464ad05308264b82dbf85686e9f16ce52698f5
Tx public key: 51022c5ee4fe3a5691967a04580486f882287f0f0a49ab4a4e1c8992ffa49139
Timestamp: 1699117662 Timestamp [UCT]: 2023-11-04 17:07:42 Age [y:d:h:m:s]: 01:157:03:19:46
Block: 884685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373246 RingCT/type: yes/0
Extra: 0151022c5ee4fe3a5691967a04580486f882287f0f0a49ab4a4e1c8992ffa4913902110000000533af99f4000000000000000000

1 output(s) for total of 0.718904746000 dcy

stealth address amount amount idx
00: 169d143da232c0e9f0e8756073e1b9cebdb22f057a9eec814b343b5c11f1b8ba 0.718904746000 1340432 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": 884695, "vin": [ { "gen": { "height": 884685 } } ], "vout": [ { "amount": 718904746, "target": { "key": "169d143da232c0e9f0e8756073e1b9cebdb22f057a9eec814b343b5c11f1b8ba" } } ], "extra": [ 1, 81, 2, 44, 94, 228, 254, 58, 86, 145, 150, 122, 4, 88, 4, 134, 248, 130, 40, 127, 15, 10, 73, 171, 74, 78, 28, 137, 146, 255, 164, 145, 57, 2, 17, 0, 0, 0, 5, 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