← previous blocknext block →recent activity
Analyzing
Block #94,816,041
16 transactions · 16 stateful · 2026-08-10 15:53:42 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,816,041 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w111w212w313w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516f4295…fad1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x91497c82…eac8
0x34b655…2a6f
6 touches
3 conflicts
0x3d222a5e…ecac
0x34b655…2a6f
6 touches
3 conflicts
0x4f394483…ff62
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
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 0x516f429509…37fad1
Audit this contract →
← previous block·next block →recent activity