← previous blocknext block →recent activity
Analyzing
Block #93,922,620
20 transactions · 18 stateful · 2026-08-07 12:42:39 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,922,620 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w212w014w315w117w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53838dd…85c9
0x34b655…2a6f
6 touches
3 conflicts
0xff68510a…09f1
0x34b655…2a6f
6 touches
3 conflicts
0x356bec59…4550
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
6 touches
3 conflicts
0x506e4e56…ca27
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x917f99a5…7989
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
3 conflicts on slot 0xc53838ddd7…b885c9
Audit this contract →
← previous block·next block →recent activity