← previous blocknext block →recent activity
Analyzing
Block #98,660,819
13 transactions · 11 stateful · 2026-08-24 04:13:28 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,660,819 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0xe06deacd…bab9
0x34b655…2a6f
8 touches
6 conflicts
0xe22455da…1ce1
0x34b655…2a6f
6 touches
3 conflicts
0x8974c003…e8cf
0x34b655…2a6f
6 touches
3 conflicts
0xb63ef486…0dcc
0x34b655…2a6f
6 touches
3 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
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 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity