← previous blocknext block →recent activity
Analyzing
Block #98,452,390
24 transactions · 24 stateful · 2026-08-23 10:15:02 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,452,390 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w08w110w011w112w213w014w316w117w218w119w220w421w322w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x88ecacda…04c9
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x86bd79a5…1f48
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity