← previous blocknext block →recent activity
Analyzing
Block #91,041,103
15 transactions · 14 stateful · 2026-07-28 11:04:39 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,041,103 · 15 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
1w04w05w16w17w28w110w011w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x7ee74e97…55f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x73f2022f…8ba2
0x34b655…2a6f
4 touches
1 conflict
0x78bb22fa…26f2
0x34b655…2a6f
4 touches
1 conflict
0x88fd7485…93c7
0x34b655…2a6f
4 touches
1 conflict
0xa8b8fbde…396d
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity