← previous blocknext block →recent activity
Analyzing
Block #95,204,820
12 transactions · 9 stateful · 2026-08-12 00:30:03 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,204,820 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x267fe70d…159e
0x34b655…2a6f
2 touches
0 conflicts
0x3661ff55…816f
0x34b655…2a6f
2 touches
0 conflicts
0x420dd604…6879
0x34b655…2a6f
2 touches
0 conflicts
0x4efae872…6aa8
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity