← previous blocknext block →recent activity

Analyzing

Block #84,510,782

20 transactions · 19 stateful · 2026-06-29 17:37:39 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,510,782  ·  20 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

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3da49e5d…8067

0x34b655…2a6f

4 touches
1 conflict

0x5fe54c42…f83f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x77dc4958…659e

0x34b655…2a6f

4 touches
1 conflict

0x7c6d3d6d…9deb

0x34b655…2a6f

4 touches
1 conflict

0x8fdfee5c…3e16

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity