← previous blocknext block →recent activity
Analyzing
Block #91,269,628
12 transactions · 11 stateful · 2026-07-29 06:14:53 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,269,628 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd3ea588…319c
0x34b655…2a6f
4 touches
1 conflict
0xdc8ace40…4daf
0x34b655…2a6f
4 touches
1 conflict
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0xf9b01e22…7e70
0x34b655…2a6f
4 touches
1 conflict
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0x1ab4c88c…49f2
0x34b655…2a6f
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x6452fb9e…f8f1
0x34b655…2a6f
4 touches
1 conflict
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 0xfd3ea588b0…ce319c
Audit this contract →
← previous block·next block →recent activity