← previous blocknext block →recent activity
Analyzing
Block #98,025,599
25 transactions · 23 stateful · 2026-08-21 22:27:01 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,025,599 · 25 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
1w02w13w04w05w110w011w112w214w015w118w219w320w423w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe196c578…6460
0x928dc8…8207
6 touches
3 conflicts
0xe196c578…6463
0x928dc8…8207
6 touches
3 conflicts
0xe196c578…6464
0x928dc8…8207
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x4508f921…7254
0xa6afd3…d132
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: 0x928dc8af…fd8207
3 conflicts on slot 0xe196c578dd…de6460
Audit this contract →
← previous block·next block →recent activity