← previous blocknext block →recent activity
Analyzing
Block #98,671,814
19 transactions · 17 stateful · 2026-08-24 05:10:42 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,671,814 · 19 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
1w02w16w27w111w012w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
11 touches
15 conflicts
0xfe20cb8f…f03d
0x34b655…2a6f
7 touches
6 conflicts
0x52998d21…303c
0x34b655…2a6f
6 touches
3 conflicts
0x575b141f…0cef
0x34b655…2a6f
5 touches
3 conflicts
0x0bd5c557…de1e
0x34b655…2a6f
5 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity