← previous blocknext block →recent activity
Analyzing
Block #95,542,357
16 transactions · 11 stateful · 2026-08-13 05:01:23 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,542,357 · 16 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
1w02w13w07w08w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xe2745681…ff50
0x3bd359…433a
2 touches
0 conflicts
0x13649b24…16e8
0x5dd8f3…c69c
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 0x9dd0a735d4…464d04
Audit this contract →
← previous block·next block →recent activity