← previous blocknext block →recent activity
Analyzing
Block #95,579,106
9 transactions · 8 stateful · 2026-08-13 08:06:13 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,579,106 · 9 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
0x4662ba80…ed23
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b688
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b689
0x34b655…2a6f
4 touches
1 conflict
0x31d7aac2…93e7
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x7f5b2c1d…0e7f
0x34b655…2a6f
2 touches
0 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
2 touches
0 conflicts
0xc5f336ca…912e
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 0x4662ba80f5…34ed23
Audit this contract →
← previous block·next block →recent activity