Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0682671e0b037c2ee07ab614d8b40ed96d0f5890e5889bbecfd125681e4848

Tx prefix hash: f561210b1fae710477edc85b4d7ae9c9a6d0513a13688f680d09a36018fd0982
Tx public key: f91844661d0099e505abfae764c1884c26ef289b1166c2811533d5f40777b52d
Timestamp: 1582989928 Timestamp [UCT]: 2020-02-29 15:25:28 Age [y:d:h:m:s]: 05:019:23:14:39
Block: 74219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168542 RingCT/type: yes/0
Extra: 01f91844661d0099e505abfae764c1884c26ef289b1166c2811533d5f40777b52d02110000001603d36d11000000000000000000

1 output(s) for total of 348.403445802000 dcy

stealth address amount amount idx
00: 4f67a7803d3f00d43392b597f3006be2990fb3df2031c5b9dd20b2a8b495bca8 348.403445802000 137231 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": 74229, "vin": [ { "gen": { "height": 74219 } } ], "vout": [ { "amount": 348403445802, "target": { "key": "4f67a7803d3f00d43392b597f3006be2990fb3df2031c5b9dd20b2a8b495bca8" } } ], "extra": [ 1, 249, 24, 68, 102, 29, 0, 153, 229, 5, 171, 250, 231, 100, 193, 136, 76, 38, 239, 40, 155, 17, 102, 194, 129, 21, 51, 213, 244, 7, 119, 181, 45, 2, 17, 0, 0, 0, 22, 3, 211, 109, 17, 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