← previous blocknext block →recent activity
Analyzing
Block #95,181,116
14 transactions · 14 stateful · 2026-08-11 22:30:50 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,181,116 · 14 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
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x3a5e95ba…806a
0x34b655…2a6f
4 touches
1 conflict
0x501f9d73…8e66
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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 0x367b69ad60…4333d9
Audit this contract →
← previous block·next block →recent activity