← previous blocknext block →recent activity

Analyzing

Block #85,459,377

19 transactions · 17 stateful · 2026-07-04 03:02:03 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,459,377  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0xfc578b53…9b1f

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x7a12283f…b18a

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

4 touches
1 conflict

0x915c095e…c1e5

0x69df8a…6292

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

15 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity