← previous blocknext block →recent activity
Analyzing
Block #98,751,672
19 transactions · 16 stateful · 2026-08-24 11:56:57 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,751,672 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w18w29w310w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5784baac…ac7e
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xafdbfc06…c2ef
0x34b655…2a6f
6 touches
3 conflicts
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xb840b390…a5a7
0x34b655…2a6f
4 touches
1 conflict
0xc0a4133e…6110
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 0x5784baac17…d4ac7e
Audit this contract →
← previous block·next block →recent activity