← previous blocknext block →recent activity
Analyzing
Block #91,955,411
17 transactions · 16 stateful · 2026-07-31 15:46:40 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,955,411 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w38w410w211w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fbda870…25a1
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1f396cee…862f
0x34b655…2a6f
8 touches
6 conflicts
0xeea8dc5f…4c68
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x1fbda8700f…f525a1
Audit this contract →
← previous block·next block →recent activity