← previous blocknext block →recent activity
Analyzing
Block #95,022,008
13 transactions · 13 stateful · 2026-08-11 09:09:42 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,022,008 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b689fd2…629c
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xb2772f3e…56cf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
3 touches
1 conflict
0x1e06b0f8…b486
0x065c9d…c394
3 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x3b689fd2ea…3f629c
Audit this contract →
← previous block·next block →recent activity