← previous blocknext block →recent activity
Analyzing
Block #98,091,830
34 transactions · 33 stateful · 2026-08-22 04:00:17 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,091,830 · 34 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
1w02w13w04w05w16w07w18w19w010w113w015w116w117w225w028w130w231w332w433w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe251ba03…50f8
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x575b141f…0cef
0x34b655…2a6f
5 touches
3 conflicts
0xdbc6e634…e169
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0xe251ba03d8…af50f8
Audit this contract →
← previous block·next block →recent activity