← previous blocknext block →recent activity

Analyzing

Block #84,622,195

25 transactions · 18 stateful · 2026-06-30 06:00:42 UTC

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,622,195  ·  25 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1062795f…b68e

0x34b655…2a6f

4 touches
1 conflict

0x24227bc5…cb16

0x34b655…2a6f

4 touches
1 conflict

0x267b5196…17ec

0x34b655…2a6f

4 touches
1 conflict

0x27d815d2…5ca9

0x34b655…2a6f

4 touches
1 conflict

0x2b6a4d72…b5c4

0x34b655…2a6f

4 touches
1 conflict

0x2fdfa032…139c

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity