← previous blocknext block →recent activity

Analyzing

Block #83,628,702

20 transactions · 19 stateful · 2026-06-25 15:37:42 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,628,702  ·  20 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

0x785889c9…0603

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x31658946…5d47

0x34b655…2a6f

4 touches
1 conflict

0x6767aeb1…eabc

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xac2a0273…721b

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 0x785889c9fb…160603

← previous block·next block →recent activity