← previous blocknext block →recent activity
Analyzing
Block #94,859,165
16 transactions · 14 stateful · 2026-08-10 19:30:39 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,859,165 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w28w310w111w412w514w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7b88d7a…b672
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0x42c27cea…b5f3
0x34b655…2a6f
6 touches
3 conflicts
0xa0bf031b…5e92
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xc7b88d7add…f4b672
Audit this contract →
← previous block·next block →recent activity