← previous blocknext block →recent activity
Analyzing
Block #98,366,449
17 transactions · 17 stateful · 2026-08-23 03:02:38 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,366,449 · 17 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
4w05w16w07w110w211w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad563cd8…d60d
0x34b655…2a6f
8 touches
6 conflicts
0x81ceb686…4df3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x61ca6437…2142
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0x90653743…d3c9
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 0xad563cd8ea…8ed60d
Audit this contract →
← previous block·next block →recent activity