Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2b71d3acf19ead92eb06628c6fb388d01fd0927691e998419b96e1b7c6e5b0

Tx prefix hash: 70c8f407a4b0bd83f272f910eae74c90405937b987179f2689ff2c6f47f6baee
Tx public key: 41705aa6add0caedb2dd0f48f8efa510a1f6795a1962d9081e1dc3554a5235b2
Timestamp: 1581993635 Timestamp [UCT]: 2020-02-18 02:40:35 Age [y:d:h:m:s]: 04:357:01:35:17
Block: 67150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147391 RingCT/type: yes/0
Extra: 0141705aa6add0caedb2dd0f48f8efa510a1f6795a1962d9081e1dc3554a5235b20211000000017adf42d3000000000000000000

1 output(s) for total of 367.709612005000 dcy

stealth address amount amount idx
00: e1157574e930c5bb53d8b7652bdb4c88ea91adedbb031fc972359ea4c121fce5 367.709612005000 123711 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": 67160, "vin": [ { "gen": { "height": 67150 } } ], "vout": [ { "amount": 367709612005, "target": { "key": "e1157574e930c5bb53d8b7652bdb4c88ea91adedbb031fc972359ea4c121fce5" } } ], "extra": [ 1, 65, 112, 90, 166, 173, 208, 202, 237, 178, 221, 15, 72, 248, 239, 165, 16, 161, 246, 121, 90, 25, 98, 217, 8, 30, 29, 195, 85, 74, 82, 53, 178, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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