← previous blocknext block →recent activity
Analyzing
Block #91,140,509
13 transactions · 13 stateful · 2026-07-28 19:24:49 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,140,509 · 13 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
6w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa38c430a…e3cb
0x34b655…2a6f
4 touches
1 conflict
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x3e2663d3…a620
0x34b655…2a6f
2 touches
0 conflicts
0x4abdde5e…461e
0x34b655…2a6f
2 touches
0 conflicts
0x59bfb0ed…ebd2
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 0xa38c430a6e…ede3cb
Audit this contract →
← previous block·next block →recent activity