← previous blocknext block →recent activity
Analyzing
Block #99,164,062
25 transactions · 23 stateful · 2026-08-25 22:38:46 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,164,062 · 25 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
1w02w13w24w35w06w48w011w015w116w217w321w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd06cc746…27e4
0x5ef52d…4343
10 touches
10 conflicts
0xa5a4bb2c…f2c7
0x188d58…ea8e
10 touches
10 conflicts
0x38aa1898…fdf5
0x3bd359…433a
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x388d69c4…4288
0x188d58…ea8e
8 touches
6 conflicts
0xd9a7cef1…1ed5
0x188d58…ea8e
8 touches
6 conflicts
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
8 touches
6 conflicts
0x1eaea4f5…6b28
0x065c9d…c394
7 touches
6 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: 0x5ef52de7…114343
10 conflicts on slot 0xd06cc7460d…e927e4
Audit this contract →
← previous block·next block →recent activity