← previous blocknext block →recent activity
Analyzing
Block #99,949,817
14 transactions · 13 stateful · 2026-08-28 16:47:36 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,949,817 · 14 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
1w02w13w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
8 touches
6 conflicts
0x46279ae7…20dd
0x2b46c0…1669
6 touches
3 conflicts
0x53e50026…6d8c
0x2b46c0…1669
6 touches
3 conflicts
0x6eff310a…c34c
0x2b46c0…1669
6 touches
3 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
6 touches
3 conflicts
0xe49b1b9b…0be1
0x2b46c0…1669
6 touches
3 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
6 conflicts on slot 0x065ff70bfe…b9356d
Audit this contract →
← previous block·next block →recent activity