← previous blocknext block →recent activity
Analyzing
Block #91,110,389
13 transactions · 13 stateful · 2026-07-28 16:53:18 UTC
Parallelism
46/100
Blocked
54%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,110,389 · 13 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
1w02w03w14w26w19w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0xa90ce2f5…308a
0x34b655…2a6f
6 touches
3 conflicts
0xbfc73ccb…386d
0x34b655…2a6f
6 touches
3 conflicts
0x7d7ff6bb…f729
0x34b655…2a6f
6 touches
3 conflicts
0xdd9c5fda…e271
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74e63d51…07ab
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity