← previous blocknext block →recent activity
Analyzing
Block #91,118,900
17 transactions · 16 stateful · 2026-07-28 17:36:06 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,118,900 · 17 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
4w05w17w110w111w212w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0x1ed748d8…d530
0x34b655…2a6f
4 touches
1 conflict
0x2d2723c7…da1c
0x34b655…2a6f
4 touches
1 conflict
0x31628334…1b92
0x34b655…2a6f
4 touches
1 conflict
0x42dfc6f5…844d
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d1
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity