Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2d76b7933931f4447f09ee25c10752e58d128cc28fe6c94ee6aea70580c904

Tx prefix hash: e02ed371bcacc4751c9bb2a8def7127624c3cda38b3bd5518f3100c7ffd23356
Tx public key: 00f19b7df875b5a4d0f4a921f273b19d1b4e9bd1cb49302ccc9ea30128b5e944
Timestamp: 1707229101 Timestamp [UCT]: 2024-02-06 14:18:21 Age [y:d:h:m:s]: 01:051:21:00:07
Block: 951666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298135 RingCT/type: yes/0
Extra: 0100f19b7df875b5a4d0f4a921f273b19d1b4e9bd1cb49302ccc9ea30128b5e94402110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68bb2a4ce317f28ff8507acd90d2eb01ee8c82bed247655cfd3610dfe24b6222 0.600000000000 1410466 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": 951676, "vin": [ { "gen": { "height": 951666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68bb2a4ce317f28ff8507acd90d2eb01ee8c82bed247655cfd3610dfe24b6222" } } ], "extra": [ 1, 0, 241, 155, 125, 248, 117, 181, 164, 208, 244, 169, 33, 242, 115, 177, 157, 27, 78, 155, 209, 203, 73, 48, 44, 204, 158, 163, 1, 40, 181, 233, 68, 2, 17, 0, 0, 0, 9, 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