← previous blocknext block →recent activity

Analyzing

Block #83,623,849

27 transactions · 24 stateful · 2026-06-25 15:05:16 UTC

Parallelism

56/100

Blocked

58%

Avg conflicts / tx

1.78

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #83,623,849  ·  27 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

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x75cdffd8…c217

0x34b655…2a6f

8 touches
6 conflicts

0xb6632320…a3ce

0x34b655…2a6f

8 touches
6 conflicts

0x124be23b…2cca

0x34b655…2a6f

6 touches
3 conflicts

0x2aa6bfcd…8e27

0x34b655…2a6f

6 touches
3 conflicts

0x3f7ad3a0…de3b

0x34b655…2a6f

6 touches
3 conflicts

0x5a5dd7b4…fba4

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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity