← previous blocknext block →recent activity

Analyzing

Block #83,401,333

20 transactions · 17 stateful · 2026-06-24 14:20:10 UTC

Parallelism

55/100

Blocked

59%

Avg conflicts / tx

1.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,401,333  ·  20 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

0x889a1747…a7ce

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x9610cea3…6614

0x34b655…2a6f

8 touches
6 conflicts

0x793aa64d…b09d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xcb89a818…e7c1

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 0x889a17478c…4ca7ce

← previous block·next block →recent activity