← previous blocknext block →recent activity

Analyzing

Block #86,628,372

23 transactions · 19 stateful · 2026-07-09 13:03:12 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,628,372  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xbde30d77…b032

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0x33d06908…0461

0x5afd3e…7620

4 touches
1 conflict

0x7fb5a9d9…9ab5

0x5afd3e…7620

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xac2a0273…721b

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 0xfaef08b108…f90696

← previous block·next block →recent activity