← previous blocknext block →recent activity
Analyzing
Block #95,727,535
11 transactions · 11 stateful · 2026-08-13 20:33:51 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,727,535 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5484fc7f…a8d8
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1fa970b3…abf8
0x34b655…2a6f
4 touches
1 conflict
0xfeb6a52b…f857
0x065c9d…c394
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 0x5484fc7fc1…98a8d8
Audit this contract →
← previous block·next block →recent activity