← previous blocknext block →recent activity
Analyzing
Block #94,868,282
16 transactions · 16 stateful · 2026-08-10 20:16:30 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,868,282 · 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
1w02w13w04w05w16w07w08w19w210w312w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa0c9bb84…ba20
0x34b655…2a6f
8 touches
6 conflicts
0x216ffe66…1f94
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity