← previous blocknext block →recent activity

Analyzing

Block #85,104,216

40 transactions · 25 stateful · 2026-07-02 11:35:38 UTC

Parallelism

90/100

Blocked

32%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,104,216  ·  40 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4560e5a8…b741

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xc4cb048e…7562

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x8bfe0643…5e5b

0x40c49f…2af0

4 touches
1 conflict

0xd16df6cd…5532

0x40c49f…2af0

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