← previous blocknext block →recent activity
Analyzing
Block #98,491,847
24 transactions · 22 stateful · 2026-08-23 13:33:53 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,491,847 · 24 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
1w02w13w24w35w17w09w110w212w013w114w316w318w422w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd1306ad…f1b8
0x34b655…2a6f
8 touches
6 conflicts
0xf1e870ad…52ae
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x6aa624fd…a84f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xcd1306adf3…44f1b8
Audit this contract →
← previous block·next block →recent activity