← previous blocknext block →recent activity

Analyzing

Block #83,029,308

26 transactions · 21 stateful · 2026-06-22 20:53:32 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,029,308  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5540f956…69e8

0x065c9d…c394

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xd2ba873b…7c9e

0xd32edf…ff58

5 touches
3 conflicts

0x6637e421…af93

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 0x5540f95607…2d69e8

← previous block·next block →recent activity