← previous blocknext block →recent activity
Analyzing
Block #91,109,544
12 transactions · 11 stateful · 2026-07-28 16:49:03 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,109,544 · 12 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
1w02w13w04w15w27w38w410w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2d93aa7c…07b9
0x34b655…2a6f
4 touches
1 conflict
0x36abaf69…6c7c
0x34b655…2a6f
4 touches
1 conflict
0x469a005e…858c
0x34b655…2a6f
4 touches
1 conflict
0x469a005e…858d
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x6d94ea59…6891
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
3 conflicts on slot 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity