← previous blocknext block →recent activity
Analyzing
Block #98,071,802
15 transactions · 15 stateful · 2026-08-22 02:19:30 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,071,802 · 15 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
1w02w13w04w17w28w29w010w112w313w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x11998eac…f9a3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity