Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02e481ac87c9265b688c828ca61ec1d549a9d8b9c0a72783ec43307aa9102d17

Tx prefix hash: aefda5af77e65b66b4fa4fb69641e64ec1c823515f1fc6993b7bfc78110a22e6
Tx public key: f5e1a507bb83ab89164f4f0a7bd65a7be9781232c82aadf616be5ab1d1ddac1e
Timestamp: 1725212131 Timestamp [UCT]: 2024-09-01 17:35:31 Age [y:d:h:m:s]: 01:063:10:22:24
Block: 1100771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303761 RingCT/type: yes/0
Extra: 01f5e1a507bb83ab89164f4f0a7bd65a7be9781232c82aadf616be5ab1d1ddac1e021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42d0e673e4df7c1b4d8faa6ac9f38539773ed0d0770e7ebe1d08c3478f4a95ff 0.600000000000 1576752 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": 1100781, "vin": [ { "gen": { "height": 1100771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42d0e673e4df7c1b4d8faa6ac9f38539773ed0d0770e7ebe1d08c3478f4a95ff" } } ], "extra": [ 1, 245, 225, 165, 7, 187, 131, 171, 137, 22, 79, 79, 10, 123, 214, 90, 123, 233, 120, 18, 50, 200, 42, 173, 246, 22, 190, 90, 177, 209, 221, 172, 30, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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