Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c41c50b4cdac20a36a14137c773ec6a1006e24458b9e747d81a810a01ce2d7

Tx prefix hash: 7523d71df54a4685cea14dc0e724e7fb0c393150aa756f3d180a4f5a5e7f97e0
Tx public key: 640827dda795b4d1515f127a1ef97f572ecdeba6466c32d4e3a3d8e841e0ff59
Timestamp: 1715438434 Timestamp [UCT]: 2024-05-11 14:40:34 Age [y:d:h:m:s]: 00:244:18:01:40
Block: 1019767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175147 RingCT/type: yes/0
Extra: 01640827dda795b4d1515f127a1ef97f572ecdeba6466c32d4e3a3d8e841e0ff59021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a3c0d4f2d7f1ebada65eed5ce65982848a6ed464fb48416fdbd2749484a538c 0.600000000000 1483808 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": 1019777, "vin": [ { "gen": { "height": 1019767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a3c0d4f2d7f1ebada65eed5ce65982848a6ed464fb48416fdbd2749484a538c" } } ], "extra": [ 1, 100, 8, 39, 221, 167, 149, 180, 209, 81, 95, 18, 122, 30, 249, 127, 87, 46, 205, 235, 166, 70, 108, 50, 212, 227, 163, 216, 232, 65, 224, 255, 89, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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