← previous blocknext block →recent activity
Analyzing
Block #91,810,233
12 transactions · 11 stateful · 2026-07-31 03:36:16 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,810,233 · 12 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ce2a0d1…e2d5
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x063a5fe9…952f
0x34b655…2a6f
2 touches
0 conflicts
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x15c6cd62…05e7
0x34b655…2a6f
2 touches
0 conflicts
0x194be77e…58ae
0x34b655…2a6f
2 touches
0 conflicts
0x1a7adb59…a2c8
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 0x0ce2a0d132…e7e2d5
Audit this contract →
← previous block·next block →recent activity