← previous blocknext block →recent activity
Analyzing
Block #98,751,490
18 transactions · 18 stateful · 2026-08-24 11:56:02 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,751,490 · 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
2w04w07w18w29w010w113w214w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c83a7b1…e305
0x34b655…2a6f
6 touches
3 conflicts
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x23529e13…6f25
0x34b655…2a6f
4 touches
1 conflict
0xc21def1b…c24d
0xa6afd3…d132
4 touches
1 conflict
0x13a260df…75e0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3f81bcfb…2905
0x40c49f…2af0
4 touches
1 conflict
0xa8087e9a…b831
0x40c49f…2af0
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 0x9c83a7b19e…36e305
Audit this contract →
← previous block·next block →recent activity