← previous blocknext block →recent activity
Analyzing
Block #91,161,186
22 transactions · 21 stateful · 2026-07-28 21:08:50 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,161,186 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w38w49w510w613w714w115w116w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x4672a4ae…e965
0x34b655…2a6f
4 touches
1 conflict
0x78cc79b1…334a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7f862c38…60a3
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity