Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4635ea1d1df8e33746906c1c473187fcc152580d650ba72985783503ea403a1e

Tx prefix hash: 3d067d7a26d4c88dad0a7a202c5a1037b43b1c759d8a595dd9a9a8074e03bb44
Tx public key: b93112fa880d2bde7f590454d3236ec52950033ea5c47aeebafc09727b106b82
Timestamp: 1643348581 Timestamp [UCT]: 2022-01-28 05:43:01 Age [y:d:h:m:s]: 04:005:14:15:28
Block: 426858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1041693 RingCT/type: yes/0
Extra: 01b93112fa880d2bde7f590454d3236ec52950033ea5c47aeebafc09727b106b8202110000000306faf294000000000000000000

1 output(s) for total of 23.639732696000 dcy

stealth address amount amount idx
00: b8e315e0201e9659a7b1df287ff262adaf4de85830fe4867013e48a92d9f83ef 23.639732696000 835828 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": 426868, "vin": [ { "gen": { "height": 426858 } } ], "vout": [ { "amount": 23639732696, "target": { "key": "b8e315e0201e9659a7b1df287ff262adaf4de85830fe4867013e48a92d9f83ef" } } ], "extra": [ 1, 185, 49, 18, 250, 136, 13, 43, 222, 127, 89, 4, 84, 211, 35, 110, 197, 41, 80, 3, 62, 165, 196, 122, 238, 186, 252, 9, 114, 123, 16, 107, 130, 2, 17, 0, 0, 0, 3, 6, 250, 242, 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