← previous blocknext block →recent activity
Analyzing
Block #98,458,693
24 transactions · 23 stateful · 2026-08-23 10:46:56 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,458,693 · 24 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
4w05w16w07w18w010w011w112w114w215w216w318w321w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfbc6d077…193b
0x34b655…2a6f
8 touches
6 conflicts
0xbceecf11…0120
0x34b655…2a6f
7 touches
6 conflicts
0x1c1b5ec9…43f6
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
6 touches
3 conflicts
0xafe91d7e…2617
0x34b655…2a6f
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
6 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity