← previous blocknext block →recent activity
Analyzing
Block #94,198,600
15 transactions · 13 stateful · 2026-08-08 11:54:01 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,198,600 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x156552f7…c066
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x9ccc60f5…00f3
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 0x156552f70b…11c066
Audit this contract →
← previous block·next block →recent activity