← previous blocknext block →recent activity
Analyzing
Block #91,103,615
23 transactions · 18 stateful · 2026-07-28 16:19:13 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,103,615 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w07w110w111w212w213w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x90d66298…42f2
0x34b655…2a6f
6 touches
3 conflicts
0xa47b7766…ee6e
0x34b655…2a6f
6 touches
3 conflicts
0x1ec8e250…0ed8
0xd32edf…ff58
5 touches
3 conflicts
0x1f8a126c…9aa1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity