← previous blocknext block →recent activity
Analyzing
Block #98,560,023
27 transactions · 24 stateful · 2026-08-23 19:28:17 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,560,023 · 27 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
1w07w18w09w110w214w015w117w218w019w120w222w223w324w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0x1408e7c7…f324
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0x4ea2d139…14b5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x905682a3…7cc2
0xd32edf…ff58
5 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity