← previous blocknext block →recent activity

Analyzing

Block #97,898,860

23 transactions · 18 stateful · 2026-08-21 11:43:48 UTC

Parallelism

87/100

Blocked

39%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,898,860  ·  23 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

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x103de0…bb55

4 touches
1 conflict

0x00000000…0003

0x103de0…bb55

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity