← previous blocknext block →recent activity
Analyzing
Block #95,173,663
14 transactions · 13 stateful · 2026-08-11 21:53:20 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,173,663 · 14 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
2w03w14w27w010w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf81cdf08…1f74
0x34b655…2a6f
8 touches
6 conflicts
0x342222e8…2ec4
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x4984f7be…d515
0x34b655…2a6f
6 touches
3 conflicts
0xba4fa3de…9d5f
0x34b655…2a6f
5 touches
3 conflicts
0xd03665ff…33bb
0x34b655…2a6f
5 touches
3 conflicts
0x91b0f8ed…6bd6
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 0xf81cdf0814…261f74
Audit this contract →
← previous block·next block →recent activity