← previous blocknext block →recent activity
Analyzing
Block #98,457,035
30 transactions · 24 stateful · 2026-08-23 10:38:33 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,457,035 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w017w219w120w223w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x301bac06…f359
0x34b655…2a6f
6 touches
3 conflicts
0xe3fbd11a…bff9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xd6071d1d…496a
0x1b6862…e19c
6 touches
3 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
3 conflicts on slot 0x301bac060b…59f359
Audit this contract →
← previous block·next block →recent activity