← previous blocknext block →recent activity
Analyzing
Block #98,668,269
38 transactions · 27 stateful · 2026-08-24 04:52:15 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,668,269 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w28w09w110w011w112w018w119w224w325w426w328w532w136w637w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x0a809ce1…7894
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0x9dd989d7…0fe2
0x34b655…2a6f
6 touches
3 conflicts
0xea7f1a23…8054
0xd32edf…ff58
5 touches
3 conflicts
0x678143da…dc6b
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity