← previous blocknext block →recent activity
Analyzing
Block #98,575,504
34 transactions · 26 stateful · 2026-08-23 20:49:15 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,575,504 · 34 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
1w02w13w04w15w26w37w08w111w012w013w116w218w119w120w022w328w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02e953d1…f2b7
0x0158ab…1a70
8 touches
6 conflicts
0x00000000…0002
0x0c428e…07a4
8 touches
6 conflicts
0x00000000…0003
0x0c428e…07a4
8 touches
6 conflicts
0x00000000…0000
0x0c428e…07a4
8 touches
6 conflicts
0x50b4806e…c048
0x3bd359…433a
8 touches
6 conflicts
0x20b50479…b75c
0x0158ab…1a70
8 touches
6 conflicts
0x7da91442…66c6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
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: 0x0158abff…731a70
6 conflicts on slot 0x02e953d126…30f2b7
Audit this contract →
← previous block·next block →recent activity