← previous blocknext block →recent activity
Analyzing
Block #98,551,218
20 transactions · 18 stateful · 2026-08-23 18:42:22 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,551,218 · 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
1w02w13w24w39w010w113w014w015w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4a9036e…9b9e
0x40c49f…2af0
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0x1408e7c7…f324
0x34b655…2a6f
4 touches
1 conflict
0xcfb87736…64ec
0x065c9d…c394
4 touches
1 conflict
0x09beabbc…065c
0x188d58…ea8e
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
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: 0x40c49f17…d22af0
3 conflicts on slot 0xc4a9036e4e…029b9e
Audit this contract →
← previous block·next block →recent activity