← previous blocknext block →recent activity
Analyzing
Block #98,749,563
28 transactions · 25 stateful · 2026-08-24 11:46:20 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,749,563 · 28 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
1w02w13w24w07w18w19w010w317w218w319w121w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbc4d3ed…2793
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0x50b0267f…6b31
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd4c913d7…3439
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: Perpl
6 conflicts on slot 0xdbc4d3ed62…262793
Audit this contract →
← previous block·next block →recent activity