Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80fd535b61cf047215ba40724aa6d65fdb96a896eb824192c4d288041ff7559a

Tx prefix hash: 221b901e7f8fa1768107aa6b6b122e9fbb4b70a3c001cb516b0e1e734acd23a4
Tx public key: a8f86ef9739463f2751927f691149a4debbae9512dff927d3c2ff46573a4018b
Timestamp: 1710030550 Timestamp [UCT]: 2024-03-10 00:29:10 Age [y:d:h:m:s]: 01:037:22:27:04
Block: 974910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288104 RingCT/type: yes/0
Extra: 01a8f86ef9739463f2751927f691149a4debbae9512dff927d3c2ff46573a4018b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e16f1a0bf48d7f8469c23acc84e03220e69eee79e59e9a2aaf6e85101bca131 0.600000000000 1434877 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": 974920, "vin": [ { "gen": { "height": 974910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e16f1a0bf48d7f8469c23acc84e03220e69eee79e59e9a2aaf6e85101bca131" } } ], "extra": [ 1, 168, 248, 110, 249, 115, 148, 99, 242, 117, 25, 39, 246, 145, 20, 154, 77, 235, 186, 233, 81, 45, 255, 146, 125, 60, 47, 244, 101, 115, 164, 1, 139, 2, 17, 0, 0, 0, 3, 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