← previous blocknext block →recent activity
Analyzing
Block #96,603,479
50 transactions · 32 stateful · 2026-08-16 22:00:22 UTC
Parallelism
74/100
Blocked
75%
Avg conflicts / tx
1.5
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #96,603,479 · 50 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w211w314w119w320w421w522w624w829w830w234w438w941w544w1248w949w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x7f68ed3c…3954
0xd32edf…ff58
11 touches
15 conflicts
0x8b41ec8f…c2d9
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity