Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8480111c904dea67436ace3100bdca1c8fa677e60949b77b8015f4902c002ccf

Tx prefix hash: b1736897c1303ef4b308075fe2ec1cacb0c151cae3b838715a7e91d5c31ba2c8
Tx public key: 92331f97eba3f21dfbd2f570a33ef21f8d91474f17c1f3264e2bf79929173a8c
Timestamp: 1712404310 Timestamp [UCT]: 2024-04-06 11:51:50 Age [y:d:h:m:s]: 01:038:14:01:39
Block: 994559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288578 RingCT/type: yes/0
Extra: 0192331f97eba3f21dfbd2f570a33ef21f8d91474f17c1f3264e2bf79929173a8c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc70ea004ab5f8cfa56726fa208213a5e436ac4e494d2275f1ea01c0c4f0ad71 0.600000000000 1454963 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": 994569, "vin": [ { "gen": { "height": 994559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc70ea004ab5f8cfa56726fa208213a5e436ac4e494d2275f1ea01c0c4f0ad71" } } ], "extra": [ 1, 146, 51, 31, 151, 235, 163, 242, 29, 251, 210, 245, 112, 163, 62, 242, 31, 141, 145, 71, 79, 23, 193, 243, 38, 78, 43, 247, 153, 41, 23, 58, 140, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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