← previous blocknext block →recent activity

Analyzing

Block #86,366,531

29 transactions · 21 stateful · 2026-07-08 07:51:33 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,366,531  ·  29 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

0x7d42dc8b…fdb6

0x2a68ba…90c5

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xbfc520c8…d31e

0x065c9d…c394

7 touches
6 conflicts

0x91af10eb…17b5

0xd32edf…ff58

7 touches
6 conflicts

0xcc8faac2…c766

0x065c9d…c394

4 touches
1 conflict

0x76945c84…3ff8

0x065c9d…c394

4 touches
1 conflict

0x2b54cadb…4425

0xd18b7e…414b

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

← previous block·next block →recent activity