← previous blocknext block →recent activity
Analyzing
Block #98,081,124
42 transactions · 39 stateful · 2026-08-22 03:06:25 UTC
Parallelism
69/100
Blocked
51%
Avg conflicts / tx
1.45
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,081,124 · 42 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
1w02w13w25w06w07w18w09w010w111w213w116w118w020w221w122w323w227w428w529w631w733w834w936w1038w1140w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfa0c5188…06f2
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity