← previous blocknext block →recent activity
Analyzing
Block #99,191,810
24 transactions · 21 stateful · 2026-08-26 00:58:23 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,191,810 · 24 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
1w02w03w110w211w313w114w215w316w017w118w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0x3b47be8b…5257
0x065c9d…c394
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x6cb5409a…dcb3
0x34b655…2a6f
4 touches
1 conflict
0x7d296c50…16b1
0x34b655…2a6f
4 touches
1 conflict
0x826444c7…583a
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity