← previous blocknext block →recent activity

Analyzing

Block #86,978,193

24 transactions · 19 stateful · 2026-07-11 04:01:52 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,978,193  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x21683d77…4e07

0x34b655…2a6f

4 touches
1 conflict

0x5238dcb7…e0e2

0x34b655…2a6f

4 touches
1 conflict

0x6d99ac64…0aa3

0x34b655…2a6f

4 touches
1 conflict

0x794443d1…2190

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x884dd0f3…2af0

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

6 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity