← previous blocknext block →recent activity
Analyzing
Block #98,842,730
29 transactions · 22 stateful · 2026-08-24 19:35:25 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,842,730 · 29 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
5w06w07w110w113w114w217w019w222w323w427w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd984a5e4…5cfc
0x34b655…2a6f
6 touches
3 conflicts
0x41335ddf…94b9
0x34b655…2a6f
6 touches
3 conflicts
0x3aca8725…5520
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
4 touches
1 conflict
0x679ef2ce…512f
0x34b655…2a6f
4 touches
1 conflict
0x68292fe7…d918
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: Market-MON/USDC
6 conflicts on slot 0x8e66da1932…c966b6
Audit this contract →
← previous block·next block →recent activity