← previous blocknext block →recent activity
Analyzing
Block #99,975,058
27 transactions · 21 stateful · 2026-08-28 18:54:45 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,975,058 · 27 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
1w03w04w17w08w09w110w212w117w221w122w223w324w326w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfd89698c…27b7
0xd32edf…ff58
5 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x50951f37…219c
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity