← previous blocknext block →recent activity
Analyzing
Block #98,752,422
25 transactions · 24 stateful · 2026-08-24 12:00:45 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,752,422 · 25 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
2w03w15w07w08w19w210w320w121w022w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0xc9860324…0ac7
0x40c49f…2af0
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
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 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity