← previous blocknext block →recent activity

Analyzing

Block #84,489,863

23 transactions · 22 stateful · 2026-06-29 15:18:01 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,489,863  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x13a54fa2…5ae3

0x2a68ba…90c5

12 touches
15 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x975680c7…0e39

0xa6afd3…d132

8 touches
6 conflicts

0x3287e4ec…eaa3

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x40970e69…da50

0x69df8a…6292

6 touches
3 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

6 touches
3 conflicts

0xb05cd4f5…73d0

0x69df8a…6292

6 touches
3 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: MarginAccount

15 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity