← previous blocknext block →recent activity

Analyzing

Block #83,455,303

24 transactions · 22 stateful · 2026-06-24 20:20:44 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

2.04

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #83,455,303  ·  24 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

0x22e0cc1d…ad0d

0x34b655…2a6f

18 touches
36 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

16 touches
28 conflicts

0x022f72c3…07b6

0xc8689a…ee79

14 touches
21 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

14 touches
21 conflicts

0xdf37a93d…879b

0x34b655…2a6f

14 touches
21 conflicts

0xffc2f21e…b393

0x34b655…2a6f

10 touches
10 conflicts

0xf2276016…945a

0x34b655…2a6f

8 touches
6 conflicts

0xe44574bf…103b

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

36 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity