← previous blocknext block →recent activity
Analyzing
Block #95,381,414
17 transactions · 16 stateful · 2026-08-12 15:30:35 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,381,414 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w06w17w28w19w010w311w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef67b8c0…deec
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3a5e95ba…806a
0x34b655…2a6f
4 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x680d2aec…8cd2
0x34b655…2a6f
4 touches
1 conflict
0x754705e8…6c85
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
3 conflicts on slot 0xef67b8c092…0fdeec
Audit this contract →
← previous block·next block →recent activity