Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76f3166ee7e451a0566d2007827054281627160abba8be43bdd2af62d4f29929

Tx prefix hash: dc7bf5bacfa040faea240dfe91c94a55b4e68cbb5e3ebab331abf2e9da4f318d
Tx public key: 4e8e4c76540799fb6526b4c9a2e5d998459acb54eb74c74f8d818659dbc5a3b6
Timestamp: 1703713462 Timestamp [UCT]: 2023-12-27 21:44:22 Age [y:d:h:m:s]: 01:104:00:53:51
Block: 922533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335467 RingCT/type: yes/0
Extra: 014e8e4c76540799fb6526b4c9a2e5d998459acb54eb74c74f8d818659dbc5a3b602110000000cad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31afdc78992867f465bd29c545ce99afac2d990dc988011c8f9e49ea71485c6d 0.600000000000 1380231 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": 922543, "vin": [ { "gen": { "height": 922533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31afdc78992867f465bd29c545ce99afac2d990dc988011c8f9e49ea71485c6d" } } ], "extra": [ 1, 78, 142, 76, 118, 84, 7, 153, 251, 101, 38, 180, 201, 162, 229, 217, 152, 69, 154, 203, 84, 235, 116, 199, 79, 141, 129, 134, 89, 219, 197, 163, 182, 2, 17, 0, 0, 0, 12, 173, 86, 148, 172, 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