← previous blocknext block →recent activity
Analyzing
Block #98,648,905
21 transactions · 19 stateful · 2026-08-24 03:11:11 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,648,905 · 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
3w04w15w26w38w39w010w011w112w213w314w415w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0x7c479858…e105
0xa6afd3…d132
11 touches
15 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfe888b58…0411
0x34b655…2a6f
6 touches
3 conflicts
0x705a9a1a…db08
0x34b655…2a6f
4 touches
1 conflict
0x77212ed8…f0c2
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
15 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity