← previous blocknext block →recent activity
Analyzing
Block #98,426,443
22 transactions · 22 stateful · 2026-08-23 08:04:29 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,426,443 · 22 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
1w02w16w17w28w010w111w119w020w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c646d87…a0a6
0x34b655…2a6f
6 touches
3 conflicts
0x385c564f…d2c2
0x34b655…2a6f
6 touches
3 conflicts
0x3f342eec…ba37
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58799a46…7030
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x6c646d879c…13a0a6
Audit this contract →
← previous block·next block →recent activity