← previous blocknext block →recent activity

Analyzing

Block #86,057,886

24 transactions · 22 stateful · 2026-07-06 21:31:09 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.46

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,057,886  ·  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

0xef65bff3…7c9d

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3d158563…8713

0x34b655…2a6f

4 touches
1 conflict

0x3e8c7016…0c69

0x34b655…2a6f

4 touches
1 conflict

0x46e5e567…ef38

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x80369a61…a879

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

3 conflicts on slot 0xef65bff33c…857c9d

← previous block·next block →recent activity