← previous blocknext block →recent activity
Analyzing
Block #96,352,520
13 transactions · 12 stateful · 2026-08-16 00:57:51 UTC
Parallelism
39/100
Blocked
67%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,352,520 · 13 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
1w02w13w04w15w27w38w49w510w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xea1b8c07…b969
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x53103bb4…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x16f2b4e1…e98b
0x34b655…2a6f
4 touches
1 conflict
0x2895e9ff…95e9
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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