Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd40a21c4e80c8779f2d6f508f0122c15a4324d8755a554a8a67166240412e0

Tx prefix hash: f133dd8b7c3771197ca9354c223d1d08fb2387dbbfd92481f781e1a3522ce9f4
Tx public key: 0739fb201c7617e053cbf0e191bc19d8d7ff0f90dc662ca3363aa0c7c89e9026
Timestamp: 1694916398 Timestamp [UCT]: 2023-09-17 02:06:38 Age [y:d:h:m:s]: 01:251:17:04:26
Block: 849784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441031 RingCT/type: yes/0
Extra: 010739fb201c7617e053cbf0e191bc19d8d7ff0f90dc662ca3363aa0c7c89e902602110000000533af99f4000000000000000000

1 output(s) for total of 0.938237750000 dcy

stealth address amount amount idx
00: b9afb713fdb3b245a278703fe1aa656f59f5277bb5e15c26b7df61bbc101a181 0.938237750000 1303466 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": 849794, "vin": [ { "gen": { "height": 849784 } } ], "vout": [ { "amount": 938237750, "target": { "key": "b9afb713fdb3b245a278703fe1aa656f59f5277bb5e15c26b7df61bbc101a181" } } ], "extra": [ 1, 7, 57, 251, 32, 28, 118, 23, 224, 83, 203, 240, 225, 145, 188, 25, 216, 215, 255, 15, 144, 220, 102, 44, 163, 54, 58, 160, 199, 200, 158, 144, 38, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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