← previous blocknext block →recent activity

Analyzing

Block #86,217,718

21 transactions · 18 stateful · 2026-07-07 15:18:00 UTC

Parallelism

90/100

Blocked

28%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,217,718  ·  21 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x2a3b7e62…fa1a

0x34b655…2a6f

4 touches
1 conflict

0x32409e80…a396

0x34b655…2a6f

4 touches
1 conflict

0x41be9e75…9773

0x34b655…2a6f

4 touches
1 conflict

0x438b0024…ce09

0x34b655…2a6f

4 touches
1 conflict

0x4ae3233a…e9f2

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

1 conflict on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity