← previous blocknext block →recent activity
Analyzing
Block #98,728,403
23 transactions · 17 stateful · 2026-08-24 09:59:53 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,728,403 · 23 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
2w03w14w25w36w011w112w217w018w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x972d632b…dff1
0x34b655…2a6f
4 touches
1 conflict
0xfb14d7f1…e509
0x34b655…2a6f
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0xf5a29f1a…d183
0x34b655…2a6f
4 touches
1 conflict
0xb20094ed…0fef
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity