Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a34d7181063a2085926da26010fa71a9317cfdd5e5c05edbd0ffcd1362252801

Tx prefix hash: 43d2d8bbd64dfe14bb0a7c643773d1e61b589009602bcd8006284b8f6bb87f6f
Tx public key: e3ee743f52c0c1ea3ebf92394c0692ebd8ca47b17f65ddecc3dab8dbd1d7a993
Timestamp: 1717695451 Timestamp [UCT]: 2024-06-06 17:37:31 Age [y:d:h:m:s]: 00:289:07:00:35
Block: 1038454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206735 RingCT/type: yes/0
Extra: 01e3ee743f52c0c1ea3ebf92394c0692ebd8ca47b17f65ddecc3dab8dbd1d7a9930211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0958c674624837113f690d24234febc047a4005428f196c16de6fd0fcf79fbe 0.600000000000 1507015 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": 1038464, "vin": [ { "gen": { "height": 1038454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0958c674624837113f690d24234febc047a4005428f196c16de6fd0fcf79fbe" } } ], "extra": [ 1, 227, 238, 116, 63, 82, 192, 193, 234, 62, 191, 146, 57, 76, 6, 146, 235, 216, 202, 71, 177, 127, 101, 221, 236, 195, 218, 184, 219, 209, 215, 169, 147, 2, 17, 0, 0, 0, 7, 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