Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0021ea66852ffe7d49d33562eb47c3dac94babaebcab9d84726c52fd435b8f90

Tx prefix hash: e2d0c6f9043093517db004ea4983c0d40bd3d8aa6d3b659d6ec1e7e37cc675e1
Tx public key: 4657b82fae6a71061d08892aa6e887dba2b8687fb9f32f3b1f7a1dec550333ed
Timestamp: 1579147561 Timestamp [UCT]: 2020-01-16 04:06:01 Age [y:d:h:m:s]: 05:034:21:32:28
Block: 46517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175069 RingCT/type: yes/0
Extra: 014657b82fae6a71061d08892aa6e887dba2b8687fb9f32f3b1f7a1dec550333ed02110000002317786bcf000000000000000000

1 output(s) for total of 430.398458255000 dcy

stealth address amount amount idx
00: e5771c345bfaaf0f1a207a2c1a3698f3dcb28c0d8a56876c9910c114168047f4 430.398458255000 85611 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": 46527, "vin": [ { "gen": { "height": 46517 } } ], "vout": [ { "amount": 430398458255, "target": { "key": "e5771c345bfaaf0f1a207a2c1a3698f3dcb28c0d8a56876c9910c114168047f4" } } ], "extra": [ 1, 70, 87, 184, 47, 174, 106, 113, 6, 29, 8, 137, 42, 166, 232, 135, 219, 162, 184, 104, 127, 185, 243, 47, 59, 31, 122, 29, 236, 85, 3, 51, 237, 2, 17, 0, 0, 0, 35, 23, 120, 107, 207, 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