← previous blocknext block →recent activity
Analyzing
Block #94,808,304
14 transactions · 13 stateful · 2026-08-10 15:14:46 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,808,304 · 14 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
2w07w09w111w212w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x154594d5…564e
0x34b655…2a6f
6 touches
3 conflicts
0x025fef2f…9738
0x34b655…2a6f
6 touches
3 conflicts
0xa8281c19…7e50
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7b409295…29bf
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xe21234e7…bded
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 0x154594d524…c7564e
Audit this contract →
← previous block·next block →recent activity