← previous blocknext block →recent activity

Analyzing

Block #84,495,727

16 transactions · 15 stateful · 2026-06-29 15:57:11 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,495,727  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d2e1791…c1dd

0x34b655…2a6f

4 touches
1 conflict

0x17d70a87…ce46

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6762cac2…3fb0

0x34b655…2a6f

4 touches
1 conflict

0x8f4c5cb2…cbee

0x34b655…2a6f

4 touches
1 conflict

0x9ad4d28a…c788

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity