Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f174de4df63a7d323cb78bd5bacc31211e7a9148760b63902ed43021130c12d

Tx prefix hash: db2920df5ba745bad30915ed5b11cc6852ee011ae94ed85dd743ec4a857f9c84
Tx public key: 90545360b5d76acf0c5db3b7e532d06c71aaa5be549af40d2af9c1d2b4b24c6b
Timestamp: 1581822475 Timestamp [UCT]: 2020-02-16 03:07:55 Age [y:d:h:m:s]: 04:315:14:52:40
Block: 65818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117924 RingCT/type: yes/0
Extra: 0190545360b5d76acf0c5db3b7e532d06c71aaa5be549af40d2af9c1d2b4b24c6b021100000003026b59f3000000000000000000

1 output(s) for total of 371.465473272000 dcy

stealth address amount amount idx
00: d940a576fee3e3704959a9825782e4db55c4da9f4ce362f7595a21114d951efb 371.465473272000 121423 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": 65828, "vin": [ { "gen": { "height": 65818 } } ], "vout": [ { "amount": 371465473272, "target": { "key": "d940a576fee3e3704959a9825782e4db55c4da9f4ce362f7595a21114d951efb" } } ], "extra": [ 1, 144, 84, 83, 96, 181, 215, 106, 207, 12, 93, 179, 183, 229, 50, 208, 108, 113, 170, 165, 190, 84, 154, 244, 13, 42, 249, 193, 210, 180, 178, 76, 107, 2, 17, 0, 0, 0, 3, 2, 107, 89, 243, 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