← previous blocknext block →recent activity

Analyzing

Block #83,617,740

27 transactions · 21 stateful · 2026-06-25 14:24:24 UTC

Parallelism

63/100

Blocked

48%

Avg conflicts / tx

1.11

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #83,617,740  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0x8d3f06db…98cb

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

6 touches
3 conflicts

0x3c9bce0e…0440

0x34b655…2a6f

6 touches
3 conflicts

0xaa6f28d9…83ef

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity