← previous blocknext block →recent activity

Analyzing

Block #86,790,274

20 transactions · 19 stateful · 2026-07-10 07:05:41 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,790,274  ·  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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x008d197a…7a6d

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x4293a398…286e

0x34b655…2a6f

4 touches
1 conflict

0x59b8078f…ecb4

0x34b655…2a6f

4 touches
1 conflict

0x66d961e5…1d87

0x34b655…2a6f

4 touches
1 conflict

0xb835d684…089c

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

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 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity