← previous blocknext block →recent activity

Analyzing

Block #84,037,681

19 transactions · 16 stateful · 2026-06-27 13:05:10 UTC

Parallelism

84/100

Blocked

38%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,037,681  ·  19 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

0x7c5260f4…bd96

0xa6afd3…d132

4 touches
1 conflict

0x1ee4a6d2…6389

0x34b655…2a6f

4 touches
1 conflict

0x3da49e5d…8067

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xcb89a818…e7c1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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