← previous blocknext block →recent activity
Analyzing
Block #92,483,188
39 transactions · 38 stateful · 2026-08-02 12:01:02 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,483,188 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w334w435w536w637w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9762d2e2…6fd6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x40ba3220…6801
0x34b655…2a6f
6 touches
3 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x9762d2e205…f46fd6
Audit this contract →
← previous block·next block →recent activity