← previous blocknext block →recent activity

Analyzing

Block #83,625,665

19 transactions · 19 stateful · 2026-06-25 15:17:22 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,625,665  ·  19 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

0xbd190ca2…e7bb

0xa6afd3…d132

5 touches
3 conflicts

0x84859a52…fbb3

0xd32edf…ff58

5 touches
3 conflicts

0xd1480c90…ae07

0x1b6862…e19c

4 touches
1 conflict

0xef65bff3…7c9d

0x2a68ba…90c5

4 touches
1 conflict

0x59d2aa91…a39a

0x34b655…2a6f

4 touches
1 conflict

0xa2c66336…c4fb

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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