← previous blocknext block →recent activity
Analyzing
Block #94,982,186
18 transactions · 18 stateful · 2026-08-11 05:49:22 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,982,186 · 18 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
1w04w06w07w18w29w010w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xbce969bb…8007
0x34b655…2a6f
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xfe605c77…361a
0x065c9d…c394
4 touches
1 conflict
0x237fbe48…657b
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity