← previous blocknext block →recent activity
Analyzing
Block #91,089,038
14 transactions · 14 stateful · 2026-07-28 15:05:52 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,089,038 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf248367d…cc48
0x34b655…2a6f
4 touches
1 conflict
0xf99d2cfb…dcdb
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity