← previous blocknext block →recent activity
Analyzing
Block #91,410,550
21 transactions · 13 stateful · 2026-07-29 18:04:41 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,410,550 · 21 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
1w02w110w012w118w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xff8fb7ba…30cc
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x64c887b9…0420
0x34b655…2a6f
4 touches
1 conflict
0x9d72189f…0cb0
0x34b655…2a6f
4 touches
1 conflict
0x4e804b48…ef71
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity