← previous blocknext block →recent activity

Analyzing

Block #83,581,604

22 transactions · 20 stateful · 2026-06-25 10:23:06 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,581,604  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

4 touches
1 conflict

0x5596b935…cc30

0x34b655…2a6f

4 touches
1 conflict

0x7d0eaae2…60b7

0x34b655…2a6f

4 touches
1 conflict

0x7e1c758b…2f47

0x34b655…2a6f

4 touches
1 conflict

0xa4658f5c…b257

0x34b655…2a6f

4 touches
1 conflict

0xbbb9fa77…d121

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

6 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity