← previous blocknext block →recent activity
Analyzing
Block #95,414,173
14 transactions · 12 stateful · 2026-08-12 18:16:24 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,414,173 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x72c6bfb7…d5cf
0x5dd8f3…c69c
2 touches
0 conflicts
0xd421a518…8b5c
0x5dd8f3…c69c
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x5f55f2c8…8f11
0x754704…b603
2 touches
0 conflicts
0x69c8bf4a…2ed0
0x754704…b603
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
1 conflict on slot 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity