← previous blocknext block →recent activity
Analyzing
Block #94,980,127
23 transactions · 22 stateful · 2026-08-11 05:39:01 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,980,127 · 23 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
3w04w15w27w38w411w012w413w121w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0xfcaee83d…428d
0x34b655…2a6f
4 touches
1 conflict
0xa98ae84b…6741
0x34b655…2a6f
4 touches
1 conflict
0xbc55e125…a9ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
15 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity