← previous blocknext block →recent activity

Analyzing

Block #84,354,688

23 transactions · 22 stateful · 2026-06-29 00:16:53 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,354,688  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3287e4ec…eaa3

0xa6afd3…d132

4 touches
1 conflict

0x1175233a…64e7

0x34b655…2a6f

4 touches
1 conflict

0x2c75ca93…a569

0x34b655…2a6f

4 touches
1 conflict

0x336a1c35…c6d5

0x34b655…2a6f

4 touches
1 conflict

0xb543d97e…cc3f

0x34b655…2a6f

4 touches
1 conflict

0xcab72563…329a

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity