← previous blocknext block →recent activity

Analyzing

Block #86,390,634

21 transactions · 20 stateful · 2026-07-08 10:32:55 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,390,634  ·  21 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

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xec2a8d79…70cb

0x34b655…2a6f

6 touches
3 conflicts

0x1ebe108b…72a0

0x34b655…2a6f

4 touches
1 conflict

0x1f668c9c…cbfb

0x34b655…2a6f

4 touches
1 conflict

0x31118d31…c786

0x34b655…2a6f

4 touches
1 conflict

0x37d710c8…45c1

0x34b655…2a6f

4 touches
1 conflict

0x3f24a374…6bc3

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

3 conflicts on slot 0xefcdf19725…1096a2

← previous block·next block →recent activity