← previous blocknext block →recent activity
Analyzing
Block #98,102,074
24 transactions · 17 stateful · 2026-08-22 04:51:50 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,102,074 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w111w113w115w216w017w121w322w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc3935765…a58e
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd9b50cd5…b4b1
0x34b655…2a6f
6 touches
3 conflicts
0xcdbc7f49…52ed
0x34b655…2a6f
6 touches
3 conflicts
0xce74d807…8716
0x34b655…2a6f
6 touches
3 conflicts
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity