← previous blocknext block →recent activity
Analyzing
Block #95,300,126
16 transactions · 14 stateful · 2026-08-12 08:38:47 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,300,126 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w29w010w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
10 touches
10 conflicts
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x598dd32b…eadd
0x34b655…2a6f
2 touches
0 conflicts
0x699ee60f…de01
0x34b655…2a6f
2 touches
0 conflicts
0x6f26fdb9…664c
0x34b655…2a6f
2 touches
0 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
10 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity