← previous blocknext block →recent activity
Analyzing
Block #98,750,096
35 transactions · 34 stateful · 2026-08-24 11:49:01 UTC
Parallelism
69/100
Blocked
41%
Avg conflicts / tx
1.29
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,750,096 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w07w08w19w010w111w215w116w218w319w424w530w732w833w934w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x6caf33e2…c261
0x34b655…2a6f
6 touches
3 conflicts
0x8c6cec40…ffd5
0x34b655…2a6f
6 touches
3 conflicts
0xc172abf1…a35c
0x34b655…2a6f
5 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity