← previous blocknext block →recent activity
Analyzing
Block #95,371,023
19 transactions · 18 stateful · 2026-08-12 14:37:58 UTC
Parallelism
58/100
Blocked
39%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,371,023 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w08w29w311w414w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
10 touches
10 conflicts
0x966e45cf…0f25
0x34b655…2a6f
8 touches
6 conflicts
0xb7fb89e5…b3c8
0x34b655…2a6f
6 touches
3 conflicts
0x5fab7fbe…1ce5
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x701208a7…46b3
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity