← previous blocknext block →recent activity
Analyzing
Block #91,796,317
12 transactions · 11 stateful · 2026-07-31 02:26:15 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,796,317 · 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
3w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c0627bd…f5c3
0x34b655…2a6f
4 touches
1 conflict
0x4c0627bd…f5c4
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0xe1b6b3c8…6676
0x34b655…2a6f
4 touches
1 conflict
0xf5a81f8f…a065
0x34b655…2a6f
4 touches
1 conflict
0x0e5d8f3e…9e79
0x34b655…2a6f
2 touches
0 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
2 touches
0 conflicts
0x3a15404b…10b1
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 0x4c0627bdf9…4ef5c3
Audit this contract →
← previous block·next block →recent activity