← previous blocknext block →recent activity
Analyzing
Block #95,381,257
19 transactions · 18 stateful · 2026-08-12 15:29:47 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,381,257 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w09w110w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x80787b19…2d69
0x34b655…2a6f
5 touches
3 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x0e37797c…d724
0x34b655…2a6f
4 touches
1 conflict
0x278c4ae5…1639
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity