← previous blocknext block →recent activity
Analyzing
Block #99,201,768
16 transactions · 16 stateful · 2026-08-26 01:48:28 UTC
Parallelism
75/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,201,768 · 16 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
1w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd0d8072d…ba4c
0x065c9d…c394
5 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x00d6e2a2…e5ca
0x065c9d…c394
2 touches
0 conflicts
0x194921ef…f6e8
0x065c9d…c394
2 touches
0 conflicts
0x1c314424…9a0c
0x065c9d…c394
2 touches
0 conflicts
0xbcee8da2…ac0c
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity