Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ae36e1caaf46bd2a991b0588dd643c4a5ca7d796437d7a99ea8859c251541c

Tx prefix hash: edc39d9d84d20e1fb4b17f19378e20a610af028a6fa21d5105eb5386012ebff4
Tx public key: 654b5792e9f1d2872a966a99c776d5e3ff7ac223ea11f4bfcc636db67ac187cf
Timestamp: 1674384387 Timestamp [UCT]: 2023-01-22 10:46:27 Age [y:d:h:m:s]: 02:111:11:55:44
Block: 680253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601350 RingCT/type: yes/0
Extra: 01654b5792e9f1d2872a966a99c776d5e3ff7ac223ea11f4bfcc636db67ac187cf021100000003272bcc39000000000000000000

1 output(s) for total of 3.420104428000 dcy

stealth address amount amount idx
00: f3fa4a475c27e8e9f3dfe2584aad149c9f87949cfc6b87ed4dbd93a407ed9023 3.420104428000 1122284 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": 680263, "vin": [ { "gen": { "height": 680253 } } ], "vout": [ { "amount": 3420104428, "target": { "key": "f3fa4a475c27e8e9f3dfe2584aad149c9f87949cfc6b87ed4dbd93a407ed9023" } } ], "extra": [ 1, 101, 75, 87, 146, 233, 241, 210, 135, 42, 150, 106, 153, 199, 118, 213, 227, 255, 122, 194, 35, 234, 17, 244, 191, 204, 99, 109, 182, 122, 193, 135, 207, 2, 17, 0, 0, 0, 3, 39, 43, 204, 57, 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