Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6e7c787feb82426c3bb5d0d0e0cacf3af3fa740bf0ca146901f8d705105925

Tx prefix hash: 1cf15585ab410da0313850f3620c72e2db0db70f6d7aa13c12733eef3b8cb528
Tx public key: e88e0f7021df290587152785c4164c770a35bdd15ef0a09407821dffd55757be
Timestamp: 1696605253 Timestamp [UCT]: 2023-10-06 15:14:13 Age [y:d:h:m:s]: 01:106:21:00:12
Block: 863805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337606 RingCT/type: yes/0
Extra: 01e88e0f7021df290587152785c4164c770a35bdd15ef0a09407821dffd55757be021100000009faf35c9c000000000000000000

1 output(s) for total of 0.843054186000 dcy

stealth address amount amount idx
00: 85ca03e43bf1e34fda6a42e3e3ab352be3be283c6d6ae7fe077d11a1b9d294f1 0.843054186000 1318299 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": 863815, "vin": [ { "gen": { "height": 863805 } } ], "vout": [ { "amount": 843054186, "target": { "key": "85ca03e43bf1e34fda6a42e3e3ab352be3be283c6d6ae7fe077d11a1b9d294f1" } } ], "extra": [ 1, 232, 142, 15, 112, 33, 223, 41, 5, 135, 21, 39, 133, 196, 22, 76, 119, 10, 53, 189, 209, 94, 240, 160, 148, 7, 130, 29, 255, 213, 87, 87, 190, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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