← previous blocknext block →recent activity
Analyzing
Block #98,660,894
20 transactions · 18 stateful · 2026-08-24 04:13:52 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,660,894 · 20 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
1w02w15w06w18w09w111w212w314w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xfd54ff1e…93c5
0x340143…768f
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x0b552eae…fbd9
0x754704…b603
4 touches
1 conflict
0x57f2a444…88a5
0x754704…b603
4 touches
1 conflict
0x5f55f2c8…8f11
0x754704…b603
4 touches
1 conflict
0x69c8bf4a…2ed0
0x754704…b603
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity