← previous blocknext block →recent activity
Analyzing
Block #96,603,905
38 transactions · 32 stateful · 2026-08-16 22:02:30 UTC
Parallelism
79/100
Blocked
66%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,603,905 · 38 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
1w02w13w24w05w37w18w29w210w311w415w516w319w328w429w432w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97862f28…4ede
0x34b655…2a6f
10 touches
10 conflicts
0xb9834665…e363
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1a287886…0266
0xa6afd3…d132
8 touches
6 conflicts
0x1803586e…d149
0xa6afd3…d132
8 touches
6 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
10 conflicts on slot 0x97862f28b8…b64ede
Audit this contract →
← previous block·next block →recent activity