← previous blocknext block →recent activity
Analyzing
Block #98,731,045
21 transactions · 20 stateful · 2026-08-24 10:13:11 UTC
Parallelism
76/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,731,045 · 21 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
1w02w13w24w35w46w18w09w212w113w014w115w216w317w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa466f3a7…02fa
0x40c49f…2af0
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xfac61869…a55c
0x1b6862…e19c
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 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: 0x40c49f17…d22af0
10 conflicts on slot 0xa466f3a7da…2e02fa
Audit this contract →
← previous block·next block →recent activity