← previous blocknext block →recent activity
Analyzing
Block #98,499,674
28 transactions · 22 stateful · 2026-08-23 14:13:27 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,499,674 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w09w010w011w112w013w116w117w219w021w122w125w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3babb490…24fc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x39773cec…38ed
0xa6afd3…d132
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x38963aeb…c33f
0xa6afd3…d132
4 touches
1 conflict
0x42e5184f…4e8b
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
3 conflicts on slot 0x3babb4900e…7f24fc
Audit this contract →
← previous block·next block →recent activity