← previous blocknext block →recent activity
Analyzing
Block #96,709,185
21 transactions · 16 stateful · 2026-08-17 06:52:00 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,709,185 · 21 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
1w02w14w25w36w414w515w616w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x24521815…c677
0x34b655…2a6f
12 touches
15 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
10 touches
10 conflicts
0x711ceb8d…5202
0x34b655…2a6f
8 touches
6 conflicts
0xe2267a44…fb98
0x34b655…2a6f
6 touches
3 conflicts
0x831dbc32…b84a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity