← previous blocknext block →recent activity
Analyzing
Block #91,247,724
11 transactions · 11 stateful · 2026-07-29 04:24:11 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,247,724 · 11 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
4w05w16w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b44
0x34b655…2a6f
4 touches
1 conflict
0x6474161a…6a37
0x34b655…2a6f
4 touches
1 conflict
0x6dea4dbf…ba54
0x34b655…2a6f
4 touches
1 conflict
0xadf6dfac…ebd8
0x34b655…2a6f
3 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity