← previous blocknext block →recent activity

Analyzing

Block #85,375,782

24 transactions · 20 stateful · 2026-07-03 17:45:26 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,375,782  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x9ff176a9…152e

0x065c9d…c394

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x5540f956…69e8

0x065c9d…c394

6 touches
3 conflicts

0x769f6332…5dd4

0x065c9d…c394

6 touches
3 conflicts

0xe4900199…4f0a

0x065c9d…c394

5 touches
3 conflicts

0x90e113f8…c8f9

0xc8689a…ee79

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-MON/USDC

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity