← previous blocknext block →recent activity
Analyzing
Block #98,388,424
19 transactions · 18 stateful · 2026-08-23 04:53:12 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,388,424 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w18w29w312w313w414w515w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58799a46…7030
0x34b655…2a6f
8 touches
6 conflicts
0xb06a48e8…d6d1
0x34b655…2a6f
6 touches
3 conflicts
0xba5cf8f6…8adf
0x34b655…2a6f
6 touches
3 conflicts
0x47fe97f9…d99b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
6 conflicts on slot 0x58799a469e…b57030
Audit this contract →
← previous block·next block →recent activity