← previous blocknext block →recent activity

Analyzing

Block #83,412,636

25 transactions · 20 stateful · 2026-06-24 15:35:42 UTC

Parallelism

52/100

Blocked

55%

Avg conflicts / tx

2.64

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #83,412,636  ·  25 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xe99d8e68…a16e

0x34b655…2a6f

24 touches
66 conflicts

0xdf37a93d…879b

0x34b655…2a6f

16 touches
28 conflicts

0x548145a9…cfce

0x34b655…2a6f

16 touches
28 conflicts

0x02bb46d3…4308

0x34b655…2a6f

15 touches
28 conflicts

0x022f72c3…07b6

0xc8689a…ee79

14 touches
21 conflicts

0xaa6f28d9…83ef

0x34b655…2a6f

14 touches
21 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

14 touches
21 conflicts

0xd06d821c…e5d0

0x34b655…2a6f

14 touches
21 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

66 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity