← previous blocknext block →recent activity
Analyzing
Block #98,645,502
24 transactions · 18 stateful · 2026-08-24 02:53:28 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,645,502 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w08w111w012w113w014w115w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd4305f3b…7f3d
0x34b655…2a6f
6 touches
3 conflicts
0x4ccbc4c3…ca6c
0x34b655…2a6f
5 touches
3 conflicts
0x48a29a03…c43c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x0b0611f77e…54e63a
Audit this contract →
← previous block·next block →recent activity