← previous blocknext block →recent activity

Analyzing

Block #86,946,307

21 transactions · 20 stateful · 2026-07-11 00:28:50 UTC

Parallelism

62/100

Blocked

60%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,946,307  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x94ed0437…073c

0x34b655…2a6f

6 touches
3 conflicts

0xa08f40b2…9a93

0x34b655…2a6f

6 touches
3 conflicts

0xfcdb5918…2b49

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x7babfe9a…ff96

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity