← previous blocknext block →recent activity
Analyzing
Block #94,960,176
16 transactions · 15 stateful · 2026-08-11 03:58:41 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,960,176 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w38w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e23360…8ef7
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
10 touches
10 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
6 touches
3 conflicts
0x36377f18…ed45
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2b988ac…37d8
0x34b655…2a6f
6 touches
3 conflicts
0x96c303ae…c7ef
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 0xf9e23360ff…e88ef7
Audit this contract →
← previous block·next block →recent activity