Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e73b7a0bbd53bef109f0d9b8ea5437d8c4bcab134c7190a8b231afcaf3fad824

Tx prefix hash: 47fac305be7d04de9631b64a21c4c7b93eba7e89be9635f16e65758c8c80f9b3
Tx public key: b5b02d07d62377eb1cc1b5cbba5cdb88725e12211169a428afdcdcb4113aeed3
Timestamp: 1762530981 Timestamp [UCT]: 2025-11-07 15:56:21 Age [y:d:h:m:s]: 00:046:12:47:02
Block: 1407032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33311 RingCT/type: yes/0
Extra: 01b5b02d07d62377eb1cc1b5cbba5cdb88725e12211169a428afdcdcb4113aeed3021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b19e774b8bf848af0ead72a778877d9d4120b791921198ae2c3aa2688b4eaebd 0.600000000000 1895439 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": 1407042, "vin": [ { "gen": { "height": 1407032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b19e774b8bf848af0ead72a778877d9d4120b791921198ae2c3aa2688b4eaebd" } } ], "extra": [ 1, 181, 176, 45, 7, 214, 35, 119, 235, 28, 193, 181, 203, 186, 92, 219, 136, 114, 94, 18, 33, 17, 105, 164, 40, 175, 220, 220, 180, 17, 58, 238, 211, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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