← previous blocknext block →recent activity

Analyzing

Block #98,848,183

20 transactions · 16 stateful · 2026-08-24 20:02:51 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,848,183  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd7443f37…eb79

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0x4baf8f3a…1758

0x34b655…2a6f

4 touches
1 conflict

0x3b7c02f2…91de

0x3bd359…433a

2 touches
0 conflicts

0xc7ea2751…3347

0x3bd359…433a

2 touches
0 conflicts

0x40fd70b1…7250

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity