← previous blocknext block →recent activity
Analyzing
Block #91,386,934
9 transactions · 8 stateful · 2026-07-29 16:05:32 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,386,934 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53cccb07…d7f0
0x34b655…2a6f
4 touches
1 conflict
0x6f4e7625…aba5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0b110f0e…022b
0x34b655…2a6f
3 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
2 touches
0 conflicts
0x2f8f103b…29f4
0x34b655…2a6f
2 touches
0 conflicts
0x383472f3…bdbc
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 0x53cccb0751…4fd7f0
Audit this contract →
← previous block·next block →recent activity