← previous blocknext block →recent activity

Analyzing

Block #83,641,757

17 transactions · 16 stateful · 2026-06-25 17:04:54 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,641,757  ·  17 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

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0xdf9957df…8d42

0x34b655…2a6f

4 touches
1 conflict

0xa1eb8469…d895

0x34b655…2a6f

4 touches
1 conflict

0xac68a0fc…2864

0xd32edf…ff58

3 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002b

0x1b6862…e19c

2 touches
0 conflicts

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