← previous blocknext block →recent activity
Analyzing
Block #92,051,373
12 transactions · 11 stateful · 2026-07-31 23:49:17 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,051,373 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56d6548…50a4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x168f7615…a8de
0x34b655…2a6f
2 touches
0 conflicts
0x4d2abe75…f42e
0x34b655…2a6f
2 touches
0 conflicts
0x4f394483…ff62
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 0xc56d654866…5050a4
Audit this contract →
← previous block·next block →recent activity