← previous blocknext block →recent activity
Analyzing
Block #98,423,587
42 transactions · 31 stateful · 2026-08-23 07:50:07 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
2.43
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,423,587 · 42 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
10w011w112w013w114w015w218w022w223w124w125w027w229w332w533w634w735w836w937w1039w1240w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xb409e204…89ac
0x34b655…2a6f
10 touches
10 conflicts
0xd33c2ab5…ccc3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7d91db0c…d41a
0x34b655…2a6f
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity