← previous blocknext block →recent activity

Analyzing

Block #84,996,758

21 transactions · 19 stateful · 2026-07-01 23:36:44 UTC

Parallelism

57/100

Blocked

47%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #84,996,758  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0xcc2cd268…5687

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x66345d58…3deb

0x34b655…2a6f

8 touches
6 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

8 touches
6 conflicts

0xd6418d68…bdc5

0x34b655…2a6f

8 touches
6 conflicts

0xdc8d4ee0…def3

0x34b655…2a6f

8 touches
6 conflicts

0xe727ab72…768b

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity