← previous blocknext block →recent activity

Analyzing

Block #86,166,357

22 transactions · 19 stateful · 2026-07-07 09:35:01 UTC

Parallelism

82/100

Blocked

32%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,166,357  ·  22 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x3bdd71a2…b6eb

0x34b655…2a6f

4 touches
1 conflict

0x480cbfe3…0476

0x34b655…2a6f

4 touches
1 conflict

0xb838bbe6…2931

0x34b655…2a6f

4 touches
1 conflict

0xffa7d0a4…b10a

0x40c49f…2af0

4 touches
1 conflict

0x157dbfb2…4089

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: Perpl

6 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity