Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e563a49c854e45b643c6cde67255ffe7e876e997c8349d583019cda4ca119d4

Tx prefix hash: d8cd8d4c07ebc20e0e5200e23ca3973cf8589dad63cd07f31e04212b6af00d69
Tx public key: 93b14ebd969cb98e6a87da7d90ccbaa09aa39e52c908e4505573f410e1d50773
Timestamp: 1726394997 Timestamp [UCT]: 2024-09-15 10:09:57 Age [y:d:h:m:s]: 00:182:16:49:04
Block: 1110569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130406 RingCT/type: yes/0
Extra: 0193b14ebd969cb98e6a87da7d90ccbaa09aa39e52c908e4505573f410e1d50773021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8805a6f00536dc2573bd38f9a3995baf0be1d9e503b10c3cdae58d628d23b485 0.600000000000 1589224 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": 1110579, "vin": [ { "gen": { "height": 1110569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8805a6f00536dc2573bd38f9a3995baf0be1d9e503b10c3cdae58d628d23b485" } } ], "extra": [ 1, 147, 177, 78, 189, 150, 156, 185, 142, 106, 135, 218, 125, 144, 204, 186, 160, 154, 163, 158, 82, 201, 8, 228, 80, 85, 115, 244, 16, 225, 213, 7, 115, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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