← previous blocknext block →recent activity
Analyzing
Block #94,685,930
14 transactions · 14 stateful · 2026-08-10 04:57:46 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,685,930 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w27w310w411w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eab7682…363a
0x34b655…2a6f
6 touches
3 conflicts
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d58476d…3e80
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x217bd767…b79e
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
3 conflicts on slot 0x6eab76823a…b0363a
Audit this contract →
← previous block·next block →recent activity