← previous blocknext block →recent activity
Analyzing
Block #98,849,441
30 transactions · 24 stateful · 2026-08-24 20:09:10 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,849,441 · 30 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
2w03w05w19w011w113w014w016w217w318w121w423w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
8 touches
6 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
8 touches
6 conflicts
0xedbcef85…9925
0x065c9d…c394
7 touches
6 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
6 touches
3 conflicts
0x7e28e55c…d05c
0x754704…b603
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 0x1125877469…519892
Audit this contract →
← previous block·next block →recent activity