← previous blocknext block →recent activity
Analyzing
Block #98,419,889
26 transactions · 22 stateful · 2026-08-23 07:31:30 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,419,889 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w115w316w017w118w019w122w023w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0xbc55e125…a9ab
0x34b655…2a6f
6 touches
3 conflicts
0x4a01d7c7…bdd5
0xd32edf…ff58
5 touches
3 conflicts
0x303f4ecc…ab9b
0x34b655…2a6f
5 touches
3 conflicts
0xea2a0ac6…f311
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity