← previous blocknext block →recent activity
Analyzing
Block #94,797,767
13 transactions · 13 stateful · 2026-08-10 14:21:46 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,797,767 · 13 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
1w02w03w15w16w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320fe488…568e
0x34b655…2a6f
6 touches
3 conflicts
0xc4d3d66a…d7a9
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0x2a58d1c6…a1a0
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0xc4d3d66a…d7a8
0x34b655…2a6f
4 touches
1 conflict
0x2de9863d…96dc
0x34b655…2a6f
2 touches
0 conflicts
0x3b689fd2…629c
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
3 conflicts on slot 0x320fe488ec…53568e
Audit this contract →
← previous block·next block →recent activity