← previous blocknext block →recent activity
Analyzing
Block #98,915,129
26 transactions · 24 stateful · 2026-08-25 01:39:38 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,915,129 · 26 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
1w02w05w19w115w019w221w322w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x886db264…846e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x36918c55…8424
0x34b655…2a6f
10 touches
10 conflicts
0x140eb1ca…bc07
0x34b655…2a6f
9 touches
10 conflicts
0x3cf099ce…2802
0x34b655…2a6f
7 touches
6 conflicts
0x00500a94…20d5
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
28 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity