← previous blocknext block →recent activity
Analyzing
Block #99,989,870
19 transactions · 19 stateful · 2026-08-28 20:09:23 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,989,870 · 19 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
3w04w15w06w17w28w09w110w112w113w214w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xb64473b0…0d6f
0xc8689a…ee79
6 touches
3 conflicts
0x6ee9bbe6…e9ac
0x40c49f…2af0
5 touches
3 conflicts
0x46279ae7…20dd
0x2b46c0…1669
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
4 touches
1 conflict
0x6eff310a…c34c
0x2b46c0…1669
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
4 touches
1 conflict
0xe49b1b9b…0be1
0x2b46c0…1669
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity