← previous blocknext block →recent activity
Analyzing
Block #91,087,912
23 transactions · 21 stateful · 2026-07-28 15:00:12 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,087,912 · 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
2w03w14w07w19w210w211w212w313w415w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x046740ca…4065
0x34b655…2a6f
4 touches
1 conflict
0x11a92863…5e7f
0x34b655…2a6f
4 touches
1 conflict
0x1c91542b…f7b1
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity