← previous blocknext block →recent activity
Analyzing
Block #98,455,436
27 transactions · 24 stateful · 2026-08-23 10:30:23 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,455,436 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w011w115w317w218w319w420w422w023w125w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f5e33f…719c
0x34b655…2a6f
10 touches
10 conflicts
0xdb2fff8d…749f
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x83f3d320…fb59
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x928d6b23…5371
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x14ca352b…7e1d
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
10 conflicts on slot 0xe8f5e33f0f…b6719c
Audit this contract →
← previous block·next block →recent activity