← previous blocknext block →recent activity

Analyzing

Block #97,914,785

18 transactions · 16 stateful · 2026-08-21 13:04:53 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,914,785  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x2daa1a87…bc59

0x40c49f…2af0

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

2 touches
0 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity