← previous blocknext block →recent activity
Analyzing
Block #98,596,290
11 transactions · 11 stateful · 2026-08-23 22:37:34 UTC
Parallelism
28/100
Blocked
64%
Avg conflicts / tx
2.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,596,290 · 11 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
3w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x080c3a8a…3088
0x34b655…2a6f
6 touches
3 conflicts
0x8ab258fd…32af
0x34b655…2a6f
6 touches
3 conflicts
0xbc55e125…a9ab
0x34b655…2a6f
5 touches
3 conflicts
0x7e59f6d5…68f0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity