← previous blocknext block →recent activity
Analyzing
Block #95,373,869
24 transactions · 20 stateful · 2026-08-12 14:52:21 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,373,869 · 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
1w02w13w27w19w010w111w012w116w217w219w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbb1bb65…4da5
0x34b655…2a6f
6 touches
3 conflicts
0xb3542864…c665
0xd32edf…ff58
5 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0xc7ee7ccc…9c56
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 0xbbb1bb6562…d64da5
Audit this contract →
← previous block·next block →recent activity