Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eeccc99f1c66fe49342f1df853b9e355dce0b5f36a21c0e37f640ce4806efbd

Tx prefix hash: e5f26bb27a47bc38594c4ef32fdfe102092f0a9e3929d56f17a0f94450e8974b
Tx public key: 1895059a3aa29737a7d2f46b401a182511d2ac0b3fcc9979432adb3d74cc71d8
Timestamp: 1581994621 Timestamp [UCT]: 2020-02-18 02:57:01 Age [y:d:h:m:s]: 05:234:05:25:18
Block: 67202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1318116 RingCT/type: yes/0
Extra: 011895059a3aa29737a7d2f46b401a182511d2ac0b3fcc9979432adb3d74cc71d802110000000312c4732d000000000000000000

1 output(s) for total of 367.563759494000 dcy

stealth address amount amount idx
00: eb01142ea8e741aa3759d1c52d036f0b2adf60ae34e034beba2fd078a56e9777 367.563759494000 123779 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": 67212, "vin": [ { "gen": { "height": 67202 } } ], "vout": [ { "amount": 367563759494, "target": { "key": "eb01142ea8e741aa3759d1c52d036f0b2adf60ae34e034beba2fd078a56e9777" } } ], "extra": [ 1, 24, 149, 5, 154, 58, 162, 151, 55, 167, 210, 244, 107, 64, 26, 24, 37, 17, 210, 172, 11, 63, 204, 153, 121, 67, 42, 219, 61, 116, 204, 113, 216, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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