← previous blocknext block →recent activity
Analyzing
Block #96,625,494
14 transactions · 12 stateful · 2026-08-16 23:51:05 UTC
Parallelism
43/100
Blocked
67%
Avg conflicts / tx
2.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,625,494 · 14 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
1w02w13w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x56153262…21ce
0x34b655…2a6f
10 touches
10 conflicts
0x12bf5c77…5588
0x34b655…2a6f
10 touches
10 conflicts
0x31616f97…1acc
0x34b655…2a6f
8 touches
6 conflicts
0xb07f01e3…0ad4
0x34b655…2a6f
8 touches
6 conflicts
0x04994ed2…9032
0x34b655…2a6f
6 touches
3 conflicts
0x4f3a6b4a…3819
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity