← previous blocknext block →recent activity
Analyzing
Block #98,746,802
30 transactions · 26 stateful · 2026-08-24 11:32:26 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,746,802 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w011w112w213w316w317w018w119w220w021w123w326w427w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x820d7282…6c34
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x354e383e…817c
0xa6afd3…d132
8 touches
6 conflicts
0xb55f6c75…c2d2
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb4c703ab…f8cf
0x34b655…2a6f
8 touches
6 conflicts
0xd068749a…79b1
0x34b655…2a6f
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
15 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity