← previous blocknext block →recent activity
Analyzing
Block #95,580,326
9 transactions · 9 stateful · 2026-08-13 08:12:21 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
1.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,580,326 · 9 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
1w02w03w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f8368a9…8eb1
0x34b655…2a6f
10 touches
10 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0x949fc5d9…55f3
0x34b655…2a6f
4 touches
1 conflict
0x87d62b39…b5ab
0x34b655…2a6f
4 touches
1 conflict
0xe624cb16…9dc0
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
10 conflicts on slot 0x6f8368a9d1…208eb1
Audit this contract →
← previous block·next block →recent activity