← previous blocknext block →recent activity

Analyzing

Block #84,265,296

19 transactions · 17 stateful · 2026-06-28 14:21:13 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,265,296  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xac61d3a4…7da8

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x07f69062…03ec

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x50f63c33…a6eb

0x34b655…2a6f

4 touches
1 conflict

0x581b829b…9578

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 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity