← previous blocknext block →recent activity
Analyzing
Block #98,733,210
18 transactions · 15 stateful · 2026-08-24 10:24:04 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,733,210 · 18 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
1w02w13w14w19w210w011w312w213w314w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xead15497…1dbe
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
6 touches
3 conflicts
0x0d85683a…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x485d2778…aa5b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xead15497a3…971dbe
Audit this contract →
← previous block·next block →recent activity