← previous blocknext block →recent activity
Analyzing
Block #98,532,763
26 transactions · 20 stateful · 2026-08-23 17:06:06 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,532,763 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w09w113w114w215w217w318w019w420w121w225w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xaf05fed7…756a
0x34b655…2a6f
6 touches
3 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0x8ac39e10…2cf8
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity