← previous blocknext block →recent activity
Analyzing
Block #95,007,188
25 transactions · 25 stateful · 2026-08-11 07:55:08 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,007,188 · 25 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
1w07w18w29w010w111w012w113w214w317w418w319w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xd3f8e9e8…2a0a
0x851145…3f07
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0x3ceaeed1…8dc0
0x34b655…2a6f
8 touches
6 conflicts
0xb9ca64a8…5597
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity