← previous blocknext block →recent activity

Analyzing

Block #86,239,366

20 transactions · 18 stateful · 2026-07-07 17:42:31 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,239,366  ·  20 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

0x7d42dc8b…fdb6

0x2a68ba…90c5

6 touches
3 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

6 touches
3 conflicts

0x64a591a8…dcbc

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3d42ebc3…2291

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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 0x7d42dc8b22…fefdb6

← previous block·next block →recent activity