← previous blocknext block →recent activity
Analyzing
Block #96,150,182
21 transactions · 18 stateful · 2026-08-15 08:00:11 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,150,182 · 21 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
3w05w17w28w39w410w411w516w620w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
12 touches
15 conflicts
0xa054b3cf…6561
0x34b655…2a6f
11 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x2fc6a7aa…b4f4
0x34b655…2a6f
10 touches
10 conflicts
0x998a1167…81f9
0x34b655…2a6f
10 touches
10 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