← previous blocknext block →recent activity
Analyzing
Block #94,979,706
19 transactions · 17 stateful · 2026-08-11 05:36:53 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,979,706 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0x34731dbd…e467
0x34b655…2a6f
6 touches
3 conflicts
0x24b6091e…d294
0x34b655…2a6f
6 touches
3 conflicts
0x5cacfb02…ef32
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x7c46fde6…d6a0
0x34b655…2a6f
4 touches
1 conflict
0x85821337…8812
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
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
15 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity