← previous blocknext block →recent activity
Analyzing
Block #99,188,208
23 transactions · 21 stateful · 2026-08-26 00:40:15 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,188,208 · 23 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
1w02w13w14w25w36w47w08w112w515w618w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x382434ca…96b5
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfd571588…2e21
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0x47bae1…7568
4 touches
1 conflict
0x00000000…0004
0x47bae1…7568
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
21 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity