← previous blocknext block →recent activity
Analyzing
Block #98,424,626
15 transactions · 13 stateful · 2026-08-23 07:55:20 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,424,626 · 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
1w02w03w07w18w29w311w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x403a4649…d8be
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2b78ba10…9ce5
0x34b655…2a6f
4 touches
1 conflict
0x3e01bb2b…00f4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x81d11f44…69b8
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 0x403a46498c…f3d8be
Audit this contract →
← previous block·next block →recent activity