← previous blocknext block →recent activity
Analyzing
Block #93,236,868
25 transactions · 21 stateful · 2026-08-05 03:14:38 UTC
Parallelism
84/100
Blocked
52%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,236,868 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w29w010w112w013w115w218w119w320w221w222w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0x5f2015cb…05b8
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf58eca50…59f9
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity