← previous blocknext block →recent activity
Analyzing
Block #98,752,812
45 transactions · 38 stateful · 2026-08-24 12:02:43 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
2.2
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,752,812 · 45 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w29w010w111w012w013w114w216w017w319w021w022w123w124w225w427w132w534w237w538w639w740w844w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xb18f9de9…c5e1
0x34b655…2a6f
6 touches
3 conflicts
0xc385d7d7…4637
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity