← previous blocknext block →recent activity
Analyzing
Block #91,433,581
12 transactions · 10 stateful · 2026-07-29 20:01:28 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,433,581 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d494c83…a65e
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x80ac2fd6…dcf5
0x34b655…2a6f
4 touches
1 conflict
0xb2b5ef74…0492
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1c0542a8…811e
0x34b655…2a6f
2 touches
0 conflicts
0x1e4b9d81…1f93
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x5d494c83bd…89a65e
Audit this contract →
← previous block·next block →recent activity