← previous blocknext block →recent activity

Analyzing

Block #84,359,699

20 transactions · 18 stateful · 2026-06-29 00:50:20 UTC

Parallelism

85/100

Blocked

39%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,359,699  ·  20 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0x0a82ef74…6501

0x34b655…2a6f

4 touches
1 conflict

0x454d8940…cfe7

0x34b655…2a6f

4 touches
1 conflict

0xa1571d54…ae41

0x34b655…2a6f

4 touches
1 conflict

0xc7fc67b1…2be3

0x34b655…2a6f

4 touches
1 conflict

0xd2274a53…9d6a

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

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