← previous blocknext block →recent activity
Analyzing
Block #95,426,622
13 transactions · 13 stateful · 2026-08-12 19:19:15 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,426,622 · 13 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
1w02w13w24w05w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8146818…5583
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x7c444b62…4063
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xe81468189b…a15583
Audit this contract →
← previous block·next block →recent activity