← previous blocknext block →recent activity
Analyzing
Block #95,154,823
16 transactions · 16 stateful · 2026-08-11 20:18:35 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,154,823 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w29w110w311w012w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc44a1acb…af47
0x34b655…2a6f
8 touches
6 conflicts
0x4174fdf9…fcfd
0x34b655…2a6f
6 touches
3 conflicts
0x48b58394…2894
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 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 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity