Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d9d72dbdb1831ee71aaf6179b25e65208f58e6769b6f5e22d4995890aded4c

Tx prefix hash: 7ce09be5e74f9a908b9386397adba749e6ce956941cd26e1be5e515e4d7b6938
Tx public key: c570f27f511064c68eeaeb54368227e8c0f05dc5f14c84c29a10ad874db4c0b9
Timestamp: 1710653172 Timestamp [UCT]: 2024-03-17 05:26:12 Age [y:d:h:m:s]: 00:315:02:07:24
Block: 980087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225477 RingCT/type: yes/0
Extra: 01c570f27f511064c68eeaeb54368227e8c0f05dc5f14c84c29a10ad874db4c0b902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecb6890eac6d305fed0a4c2231bb9f573073b54596623ef0aeed1fb28d1f47db 0.600000000000 1440146 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": 980097, "vin": [ { "gen": { "height": 980087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecb6890eac6d305fed0a4c2231bb9f573073b54596623ef0aeed1fb28d1f47db" } } ], "extra": [ 1, 197, 112, 242, 127, 81, 16, 100, 198, 142, 234, 235, 84, 54, 130, 39, 232, 192, 240, 93, 197, 241, 76, 132, 194, 154, 16, 173, 135, 77, 180, 192, 185, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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