← previous blocknext block →recent activity
Analyzing
Block #95,123,765
25 transactions · 25 stateful · 2026-08-11 17:42:22 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,123,765 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w38w49w511w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5dee77e…0df7
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
8 touches
6 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0x57e2ff7d…f55a
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xc5dee77e6d…3f0df7
Audit this contract →
← previous block·next block →recent activity