← previous blocknext block →recent activity
Analyzing
Block #95,586,599
16 transactions · 16 stateful · 2026-08-13 08:43:54 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,586,599 · 16 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
1w03w04w05w17w19w210w311w312w214w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
10 touches
10 conflicts
0xbd7a050e…fba8
0x34b655…2a6f
6 touches
3 conflicts
0x7e3cc3e1…ced8
0x34b655…2a6f
6 touches
3 conflicts
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x82d510df…8d5c
0x34b655…2a6f
4 touches
1 conflict
0x89b7c544…35e0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
10 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity