← previous blocknext block →recent activity
Analyzing
Block #99,879,677
35 transactions · 29 stateful · 2026-08-28 10:54:06 UTC
Parallelism
89/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,879,677 · 35 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
1w04w06w09w110w211w112w115w217w218w121w022w123w327w129w230w031w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70d81211…f49f
0x34b655…2a6f
8 touches
6 conflicts
0x51af0e92…4020
0x34b655…2a6f
6 touches
3 conflicts
0xdb40334f…e0bc
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x28d6519c…31f5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
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
6 conflicts on slot 0x70d812119d…c1f49f
Audit this contract →
← previous block·next block →recent activity