Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0470022b0262c0251afd5f4e519500a5012bd966a9f65981cc63eaa82e8243

Tx prefix hash: 6f696bde7e6d9723b1bd6f91542e40cc59cb68424f386592b2ef77dd49d021f7
Tx public key: ae076e485f3ac13c12aa47d84816b7843814f9b7c578171511973f8df12dc65c
Timestamp: 1580977354 Timestamp [UCT]: 2020-02-06 08:22:34 Age [y:d:h:m:s]: 04:362:04:39:14
Block: 59718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150072 RingCT/type: yes/0
Extra: 01ae076e485f3ac13c12aa47d84816b7843814f9b7c578171511973f8df12dc65c021100000003c71d3ff9000000000000000000

1 output(s) for total of 389.168591672000 dcy

stealth address amount amount idx
00: c1f470a59edaaf90d68ce693792e466c0f1786623e562f6e56160ed063140720 389.168591672000 110197 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": 59728, "vin": [ { "gen": { "height": 59718 } } ], "vout": [ { "amount": 389168591672, "target": { "key": "c1f470a59edaaf90d68ce693792e466c0f1786623e562f6e56160ed063140720" } } ], "extra": [ 1, 174, 7, 110, 72, 95, 58, 193, 60, 18, 170, 71, 216, 72, 22, 183, 132, 56, 20, 249, 183, 197, 120, 23, 21, 17, 151, 63, 141, 241, 45, 198, 92, 2, 17, 0, 0, 0, 3, 199, 29, 63, 249, 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