← previous blocknext block →recent activity
Analyzing
Block #95,025,148
13 transactions · 9 stateful · 2026-08-11 09:25:29 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,025,148 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fdfa820…7b4b
0x34b655…2a6f
4 touches
1 conflict
0x2b64d0d7…af06
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2e9d65ac…2265
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2266
0x34b655…2a6f
2 touches
0 conflicts
0x71dbb1f4…7223
0x34b655…2a6f
2 touches
0 conflicts
0x8d93c73d…e398
0x34b655…2a6f
2 touches
0 conflicts
0xbcbf5d09…8bac
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
1 conflict on slot 0x5fdfa820c5…2d7b4b
Audit this contract →
← previous block·next block →recent activity