← previous blocknext block →recent activity
Analyzing
Block #96,664,536
16 transactions · 14 stateful · 2026-08-17 03:07:27 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,664,536 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w210w311w412w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0xd597209e…9800
0x34b655…2a6f
4 touches
1 conflict
0x03db0fbf…d5b9
0x34b655…2a6f
4 touches
1 conflict
0x21170416…c384
0x34b655…2a6f
4 touches
1 conflict
0x437104d2…66a2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8861b270…e0cb
0x34b655…2a6f
4 touches
1 conflict
0x8c1b3662…8075
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
6 conflicts on slot 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity