← previous blocknext block →recent activity
Analyzing
Block #96,150,610
11 transactions · 10 stateful · 2026-08-15 08:02:20 UTC
Parallelism
45/100
Blocked
50%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,150,610 · 11 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b17f7a0…af41
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x2895e9ff…95e9
0x34b655…2a6f
6 touches
3 conflicts
0x7ac265cd…0253
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x4abaedb1…65b9
0x34b655…2a6f
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
15 conflicts on slot 0x6b17f7a0cf…37af41
Audit this contract →
← previous block·next block →recent activity