Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d536b38b907f123822c26abbbea1e2a1ff8f04590f3fe6f351912bcc425106

Tx prefix hash: 082c7c36b65a4aeb0ce93a1f1524938368a2767f2daf71d68c151fd83f402964
Tx public key: a42058b380801e941cd3789b428c71f8aa0ae5988e92c42f2f039c9a931b1600
Timestamp: 1709219648 Timestamp [UCT]: 2024-02-29 15:14:08 Age [y:d:h:m:s]: 01:047:04:04:18
Block: 968190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294719 RingCT/type: yes/0
Extra: 01a42058b380801e941cd3789b428c71f8aa0ae5988e92c42f2f039c9a931b16000211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab1ce6c1589eec17988695ff95a8037587694c63053aa63ff55c72514f83e0f2 0.600000000000 1427991 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": 968200, "vin": [ { "gen": { "height": 968190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab1ce6c1589eec17988695ff95a8037587694c63053aa63ff55c72514f83e0f2" } } ], "extra": [ 1, 164, 32, 88, 179, 128, 128, 30, 148, 28, 211, 120, 155, 66, 140, 113, 248, 170, 10, 229, 152, 142, 146, 196, 47, 47, 3, 156, 154, 147, 27, 22, 0, 2, 17, 0, 0, 0, 5, 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