← previous blocknext block →recent activity
Analyzing
Block #98,148,428
37 transactions · 32 stateful · 2026-08-22 08:45:46 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.92
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,148,428 · 37 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w09w010w115w018w120w021w124w225w326w427w528w629w730w831w932w1033w1134w1236w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x6f1bd077…2005
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity