← previous blocknext block →recent activity
Analyzing
Block #91,780,418
14 transactions · 13 stateful · 2026-07-31 01:06:16 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,780,418 · 14 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
2w06w07w18w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6083af24…a0df
0x34b655…2a6f
4 touches
1 conflict
0x829041ba…9a15
0x34b655…2a6f
4 touches
1 conflict
0x53699236…fede
0x34b655…2a6f
4 touches
1 conflict
0x922e7a8d…7cff
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe6a34ca2…4075
0x34b655…2a6f
4 touches
1 conflict
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
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 0x6083af2440…5fa0df
Audit this contract →
← previous block·next block →recent activity