Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38428eede56f0a6381fb6774fe977bea26866720a2baf768010267ac51521726

Tx prefix hash: 560aa619fe6796d456eb5650ae6b3bd307b32da93398aacd82c7960da8a94161
Tx public key: 9a0daee3d8a49280d6e53511e6aa9c977efa0f09ab0ef54f8870d4eef6db6ae8
Timestamp: 1715827682 Timestamp [UCT]: 2024-05-16 02:48:02 Age [y:d:h:m:s]: 00:352:06:00:38
Block: 1022971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251794 RingCT/type: yes/0
Extra: 019a0daee3d8a49280d6e53511e6aa9c977efa0f09ab0ef54f8870d4eef6db6ae802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19c3b0d7614ceb7987c3e73d70055f71cc6cb73008e54f1c854c932bb0498d43 0.600000000000 1487726 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": 1022981, "vin": [ { "gen": { "height": 1022971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19c3b0d7614ceb7987c3e73d70055f71cc6cb73008e54f1c854c932bb0498d43" } } ], "extra": [ 1, 154, 13, 174, 227, 216, 164, 146, 128, 214, 229, 53, 17, 230, 170, 156, 151, 126, 250, 15, 9, 171, 14, 245, 79, 136, 112, 212, 238, 246, 219, 106, 232, 2, 17, 0, 0, 0, 3, 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