← previous blocknext block →recent activity
Analyzing
Block #96,512,216
16 transactions · 14 stateful · 2026-08-16 14:21:21 UTC
Parallelism
44/100
Blocked
64%
Avg conflicts / tx
2.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,512,216 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w49w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
14 touches
21 conflicts
0xff196840…a453
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
8 touches
6 conflicts
0xb88ac6bf…868e
0x34b655…2a6f
7 touches
6 conflicts
0x83f3d320…fb59
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity