← previous blocknext block →recent activity
Analyzing
Block #95,655,157
28 transactions · 27 stateful · 2026-08-13 14:28:45 UTC
Parallelism
64/100
Blocked
56%
Avg conflicts / tx
1.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #95,655,157 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w09w110w311w412w513w616w417w718w824w627w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3da5cba…0d68
0x34b655…2a6f
8 touches
6 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
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
6 conflicts on slot 0xa3da5cba5b…0f0d68
Audit this contract →
← previous block·next block →recent activity