← previous blocknext block →recent activity
Analyzing
Block #95,405,850
16 transactions · 14 stateful · 2026-08-12 17:34:15 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,405,850 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
4 touches
1 conflict
0x5cacfb02…ef32
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x729c91b8…953a
0x188d58…ea8e
2 touches
0 conflicts
0xf8704666…c34c
0x188d58…ea8e
2 touches
0 conflicts
0xf8704666…c34d
0x188d58…ea8e
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
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity