Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34e041a1034d50a561e0ff144d23b2d399afeb6fc9b3e5c313f1b83d4192e2d6

Tx prefix hash: 0d8a622deebb422ff3aaed5499364cf90aa0125ef99141e3fbdf93992f1b01de
Tx public key: f1efe39140dde65c2c7fa222d85ab44a1c15c7f0bcb0af6c76d1c4c66df26a2e
Timestamp: 1725291838 Timestamp [UCT]: 2024-09-02 15:43:58 Age [y:d:h:m:s]: 00:233:01:51:16
Block: 1101429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166434 RingCT/type: yes/0
Extra: 01f1efe39140dde65c2c7fa222d85ab44a1c15c7f0bcb0af6c76d1c4c66df26a2e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d694c2b052fb0b25ec1ebe61861ee9af73273e9106e088e4872612c9aaf5599c 0.600000000000 1577474 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": 1101439, "vin": [ { "gen": { "height": 1101429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d694c2b052fb0b25ec1ebe61861ee9af73273e9106e088e4872612c9aaf5599c" } } ], "extra": [ 1, 241, 239, 227, 145, 64, 221, 230, 92, 44, 127, 162, 34, 216, 90, 180, 74, 28, 21, 199, 240, 188, 176, 175, 108, 118, 209, 196, 198, 109, 242, 106, 46, 2, 17, 0, 0, 0, 5, 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