← previous blocknext block →recent activity

Analyzing

Block #83,630,065

27 transactions · 24 stateful · 2026-06-25 15:46:47 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,630,065  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x8d3f06db…98cb

0x34b655…2a6f

6 touches
3 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x75291f8b…3ac0

0x34b655…2a6f

5 touches
3 conflicts

0xaeb1c015…e917

0x34b655…2a6f

4 touches
1 conflict

0xef65bff3…7c9d

0x2a68ba…90c5

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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity