← previous blocknext block →recent activity
Analyzing
Block #95,566,447
23 transactions · 22 stateful · 2026-08-13 07:02:33 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,566,447 · 23 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
1w02w13w04w15w16w27w39w411w014w215w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x2491d756…b71c
0xa6afd3…d132
6 touches
3 conflicts
0x6847107a…f468
0xa6afd3…d132
6 touches
3 conflicts
0x43fd3667…094b
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x3c5ea1e9…7e5a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity