← previous blocknext block →recent activity

Analyzing

Block #84,511,439

20 transactions · 20 stateful · 2026-06-29 17:42:02 UTC

Parallelism

85/100

Blocked

20%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,511,439  ·  20 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x9a291a56…9a9c

0x34b655…2a6f

4 touches
1 conflict

0x08cc68a2…2a59

0x34b655…2a6f

4 touches
1 conflict

0x7b9a42f7…7b88

0xa6afd3…d132

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xcfe06a18…b5b5

0x69df8a…6292

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: MarginAccount

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity