← previous blocknext block →recent activity
Analyzing
Block #95,552,368
24 transactions · 18 stateful · 2026-08-13 05:51:44 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,552,368 · 24 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
2w03w14w29w010w113w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69c491e3…98d9
0x34b655…2a6f
6 touches
3 conflicts
0xe20cfb89…cd07
0x754704…b603
6 touches
3 conflicts
0xdc255d21…c377
0x754704…b603
6 touches
3 conflicts
0xaad1c5c0…ab91
0x754704…b603
6 touches
3 conflicts
0x44b80fe8…bfa7
0x34b655…2a6f
4 touches
1 conflict
0x458b9085…9ee2
0x34b655…2a6f
4 touches
1 conflict
0xa0756a9b…7699
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x69c491e302…ce98d9
Audit this contract →
← previous block·next block →recent activity