← previous blocknext block →recent activity
Analyzing
Block #99,857,940
22 transactions · 19 stateful · 2026-08-28 09:04:35 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,857,940 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w07w18w29w310w412w413w115w116w518w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x6c5d37d3…a29a
0x34b655…2a6f
4 touches
1 conflict
0x80c79cb7…91d0
0x34b655…2a6f
4 touches
1 conflict
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0xc16e646d…4fb0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity