← previous blocknext block →recent activity
Analyzing
Block #98,552,261
23 transactions · 17 stateful · 2026-08-23 18:47:44 UTC
Parallelism
91/100
Blocked
12%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,552,261 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w111w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25756067…585d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x642a3b52…ea7a
0xd32edf…ff58
3 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x6d352690…6b75
0x3bd359…433a
2 touches
0 conflicts
0x57ddf79e…683c
0x754704…b603
2 touches
0 conflicts
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: Market-MON/USDC
1 conflict on slot 0x25756067dc…3f585d
Audit this contract →
← previous block·next block →recent activity