← previous blocknext block →recent activity
Analyzing
Block #92,393,685
12 transactions · 10 stateful · 2026-08-02 04:30:52 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,393,685 · 12 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xb6ea4726…5140
0x34b655…2a6f
4 touches
1 conflict
0x02863d03…c9d6
0x34b655…2a6f
2 touches
0 conflicts
0x16eae56b…db07
0x34b655…2a6f
2 touches
0 conflicts
0x203ee01b…e1d9
0x34b655…2a6f
2 touches
0 conflicts
0x3aac0597…8e4a
0x34b655…2a6f
2 touches
0 conflicts
0x4b8db3ce…d59b
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity