← previous blocknext block →recent activity
Analyzing
Block #95,985,429
16 transactions · 16 stateful · 2026-08-14 18:11:19 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
2.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,985,429 · 16 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
1w02w03w14w25w38w49w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x07010ea7…c45a
0x34b655…2a6f
10 touches
10 conflicts
0xea1b8c07…b969
0x34b655…2a6f
10 touches
10 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
6 touches
3 conflicts
0xaafc0c3d…64b6
0x34b655…2a6f
6 touches
3 conflicts
0xad843ea4…ad90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity