← previous blocknext block →recent activity
Analyzing
Block #91,132,042
10 transactions · 8 stateful · 2026-07-28 18:42:13 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,132,042 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x320b9f7c…3fec
0x34b655…2a6f
2 touches
0 conflicts
0x33f2f11d…2d48
0x34b655…2a6f
2 touches
0 conflicts
0x36e7818c…c2ea
0x34b655…2a6f
2 touches
0 conflicts
0x37da952b…0782
0x34b655…2a6f
2 touches
0 conflicts
0x3a6aab02…1436
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity