← previous blocknext block →recent activity
Analyzing
Block #92,539,411
7 transactions · 7 stateful · 2026-08-02 16:43:46 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,539,411 · 7 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
1w02w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf869897e…5965
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x24beab0f…ee70
0x34b655…2a6f
2 touches
0 conflicts
0xc825238c…ee92
0x34b655…2a6f
2 touches
0 conflicts
0x4fb86cd0…c67b
0x34b655…2a6f
2 touches
0 conflicts
0x4fb86cd0…c67c
0x34b655…2a6f
2 touches
0 conflicts
0x5649379f…d9eb
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 0xf869897e5e…075965
Audit this contract →
← previous block·next block →recent activity