← previous blocknext block →recent activity
Analyzing
Block #98,507,038
24 transactions · 18 stateful · 2026-08-23 14:51:43 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,507,038 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w013w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x71ab2d1a…af06
0x34b655…2a6f
6 touches
3 conflicts
0xdbc44cfb…577d
0xd32edf…ff58
5 touches
3 conflicts
0x483c2974…bee4
0x34b655…2a6f
4 touches
1 conflict
0x640c4fb2…044a
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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
3 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity