← previous blocknext block →recent activity
Analyzing
Block #96,611,487
18 transactions · 16 stateful · 2026-08-16 22:40:39 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,611,487 · 18 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
1w02w03w04w16w07w18w29w110w211w312w413w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247efa85…c7b4
0x34b655…2a6f
12 touches
15 conflicts
0xca2926e0…61b5
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
8 touches
6 conflicts
0x4acc6dca…a868
0x34b655…2a6f
6 touches
3 conflicts
0x784eaad2…d176
0x34b655…2a6f
6 touches
3 conflicts
0x9ca6fa7b…aeb3
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
15 conflicts on slot 0x247efa8544…1dc7b4
Audit this contract →
← previous block·next block →recent activity