← previous blocknext block →recent activity
Analyzing
Block #98,500,702
26 transactions · 21 stateful · 2026-08-23 14:18:48 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,500,702 · 26 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
1w03w04w16w114w015w117w218w219w220w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcc15d874…7c69
0xd32edf…ff58
5 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0x0af22aa9…087d
0x34b655…2a6f
4 touches
1 conflict
0x38963aeb…c33f
0xa6afd3…d132
4 touches
1 conflict
0x2bfc672f…4d29
0x34b655…2a6f
4 touches
1 conflict
0x2cfe7c05…2b42
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity