Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85445e3cb74cbf93ca674dd43fb74945026b933ecb9fe5ff2d2ba2a08a52564e

Tx prefix hash: 80c0af161d1e4acd85ad5b33d7a81432ccbd964d36b2a9cdc50ff71282c36ee7
Tx public key: 67ae4ea06eabc5b7835b00b24e57df45b5b3d8cd10fd7ecf2e7e5bcf8900cf37
Timestamp: 1705056220 Timestamp [UCT]: 2024-01-12 10:43:40 Age [y:d:h:m:s]: 01:355:09:05:27
Block: 933647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512887 RingCT/type: yes/0
Extra: 0167ae4ea06eabc5b7835b00b24e57df45b5b3d8cd10fd7ecf2e7e5bcf8900cf3702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 027e4d4174b74733ba43e4d388549225d769e8608bf5e88e1c57eff6ee7af19f 0.600000000000 1391617 of 15

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": 933657, "vin": [ { "gen": { "height": 933647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "027e4d4174b74733ba43e4d388549225d769e8608bf5e88e1c57eff6ee7af19f" } } ], "extra": [ 1, 103, 174, 78, 160, 110, 171, 197, 183, 131, 91, 0, 178, 78, 87, 223, 69, 181, 179, 216, 205, 16, 253, 126, 207, 46, 126, 91, 207, 137, 0, 207, 55, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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