← previous blocknext block →recent activity
Analyzing
Block #95,300,851
10 transactions · 9 stateful · 2026-08-12 08:42:27 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,300,851 · 10 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
1w02w13w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f394483…ff62
0x34b655…2a6f
6 touches
3 conflicts
0xfe3d2a2f…6b7b
0x34b655…2a6f
6 touches
3 conflicts
0xe6c39281…a29a
0x34b655…2a6f
4 touches
1 conflict
0xe74deb99…9e5b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x2592d715…a50e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
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 0x4f39448303…4fff62
Audit this contract →
← previous block·next block →recent activity