← previous blocknext block →recent activity
Analyzing
Block #99,278,975
21 transactions · 19 stateful · 2026-08-26 08:16:59 UTC
Parallelism
86/100
Blocked
16%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,278,975 · 21 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
1w04w06w07w114w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2629d3b0…ce5d
0x065c9d…c394
2 touches
0 conflicts
0x449117cc…6e58
0x065c9d…c394
2 touches
0 conflicts
0x46c16654…5478
0x065c9d…c394
2 touches
0 conflicts
0x84982930…08c8
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 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: Perpl
3 conflicts on slot 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity