← previous blocknext block →recent activity
Analyzing
Block #94,960,183
22 transactions · 21 stateful · 2026-08-11 03:58:43 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,960,183 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w38w49w010w111w412w113w214w315w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e23360…8ef7
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x059bff94…6c87
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
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 0xf9e23360ff…e88ef7
Audit this contract →
← previous block·next block →recent activity