← previous blocknext block →recent activity

Analyzing

Block #85,143,856

24 transactions · 21 stateful · 2026-07-02 16:00:39 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,143,856  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x2886e2bc…6ab8

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3e1c3586…83d7

0xa6afd3…d132

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x6b077d96…0152

0x34b655…2a6f

4 touches
1 conflict

0x803204dc…bc7a

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

10 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity