← previous blocknext block →recent activity

Analyzing

Block #83,455,070

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

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,455,070  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x09a4820b…2db8

0x34b655…2a6f

4 touches
1 conflict

0x126a0344…4465

0x34b655…2a6f

4 touches
1 conflict

0x2a93c65a…711f

0x34b655…2a6f

4 touches
1 conflict

0x2b2dce58…2f1d

0x34b655…2a6f

4 touches
1 conflict

0x2d95c7ff…1596

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity