← previous blocknext block →recent activity
Analyzing
Block #98,366,336
18 transactions · 17 stateful · 2026-08-23 03:02:04 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,366,336 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w09w110w211w112w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d9bd728…dda2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0x48a0f121…953b
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0x00a2ea07…ee29
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x5d9bd728f6…9ddda2
Audit this contract →
← previous block·next block →recent activity