← previous blocknext block →recent activity
Analyzing
Block #95,528,535
14 transactions · 13 stateful · 2026-08-13 03:51:52 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,528,535 · 14 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
1w02w13w24w36w07w18w39w210w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
6 touches
3 conflicts
0xd08c6080…0af2
0x34b655…2a6f
6 touches
3 conflicts
0xad631952…e126
0x34b655…2a6f
6 touches
3 conflicts
0x4e697adf…0ac0
0x34b655…2a6f
6 touches
3 conflicts
0x11f5dd1d…1548
0xa6afd3…d132
5 touches
3 conflicts
0x5fde4971…aac9
0x34b655…2a6f
4 touches
1 conflict
0x7f443062…03c5
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity