← previous blocknext block →recent activity

Analyzing

Block #86,978,315

19 transactions · 18 stateful · 2026-07-11 04:02:41 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.79

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,978,315  ·  19 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x363a4317…87d2

0x34b655…2a6f

6 touches
3 conflicts

0x5fee1ba0…2520

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x2fa2e180…87a9

0x34b655…2a6f

6 touches
3 conflicts

0xb548e430…adbc

0x34b655…2a6f

6 touches
3 conflicts

0xbfdd8306…fa07

0x34b655…2a6f

6 touches
3 conflicts

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity