← previous blocknext block →recent activity
Analyzing
Block #95,203,564
5 transactions · 5 stateful · 2026-08-12 00:23:44 UTC
Parallelism
20/100
Blocked
60%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,203,564 · 5 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99d2cfb…dcdb
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x1af644dc…0822
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1507536e…933f
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63b
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63c
0x34b655…2a6f
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
3 conflicts on slot 0xf99d2cfbd5…94dcdb
Audit this contract →
← previous block·next block →recent activity