← previous blocknext block →recent activity
Analyzing
Block #98,642,473
21 transactions · 21 stateful · 2026-08-24 02:37:46 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,642,473 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w19w210w311w412w515w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a9e9bd1…5368
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xc60f31ed…400b
0xa6afd3…d132
9 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
10 conflicts on slot 0x2a9e9bd1e2…355368
Audit this contract →
← previous block·next block →recent activity