← previous blocknext block →recent activity
Analyzing
Block #99,361,789
30 transactions · 18 stateful · 2026-08-26 15:13:44 UTC
Parallelism
90/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,361,789 · 30 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
1w03w07w19w013w017w018w120w121w023w124w127w228w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3a1ede2b…a396
0x065c9d…c394
4 touches
1 conflict
0x09beabbc…065c
0x188d58…ea8e
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity