Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391f07f8823b7563c008e31108c62e0cf3299ab2e9a2a9cd2008fcacbdd1c1ed

Tx prefix hash: 593785c37ccb0310033b46e258442b1198919ad5d2fb83e578d887877fd30d17
Tx public key: af3cf3886124b1f53a39a9f1d22843e62eb6176c8080e07749f3d703a24b8348
Timestamp: 1632333806 Timestamp [UCT]: 2021-09-22 18:03:26 Age [y:d:h:m:s]: 03:217:09:05:00
Block: 338945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 931354 RingCT/type: yes/0
Extra: 01af3cf3886124b1f53a39a9f1d22843e62eb6176c8080e07749f3d703a24b834802110000002936fe6557000000000000000000

1 output(s) for total of 46.231176536000 dcy

stealth address amount amount idx
00: 0c90b57c89dca26e07ed02815fc15c0b95f92e5e7d1153c7344ed8cf38a58f1f 46.231176536000 697334 of 0

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": 338955, "vin": [ { "gen": { "height": 338945 } } ], "vout": [ { "amount": 46231176536, "target": { "key": "0c90b57c89dca26e07ed02815fc15c0b95f92e5e7d1153c7344ed8cf38a58f1f" } } ], "extra": [ 1, 175, 60, 243, 136, 97, 36, 177, 245, 58, 57, 169, 241, 210, 40, 67, 230, 46, 182, 23, 108, 128, 128, 224, 119, 73, 243, 215, 3, 162, 75, 131, 72, 2, 17, 0, 0, 0, 41, 54, 254, 101, 87, 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