← previous blocknext block →recent activity
Analyzing
Block #96,837,643
14 transactions · 13 stateful · 2026-08-17 17:38:07 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,837,643 · 14 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
1w02w13w24w05w26w08w310w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
10 touches
10 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0x1244b105…8e9c
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity