← previous blocknext block →recent activity
Analyzing
Block #98,271,386
26 transactions · 25 stateful · 2026-08-22 19:04:21 UTC
Parallelism
42/100
Blocked
64%
Avg conflicts / tx
3.38
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,271,386 · 26 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w010w111w212w213w314w415w516w617w718w819w920w1021w1122w1223w1324w1425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x886db264…846e
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x859c92cc…430b
0x34b655…2a6f
8 touches
6 conflicts
0x0bd5c557…de1e
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity