← previous blocknext block →recent activity

Analyzing

Block #84,491,090

20 transactions · 18 stateful · 2026-06-29 15:26:13 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,491,090  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xda7f9bd2…e332

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x3614b052…4e53

0x34b655…2a6f

6 touches
3 conflicts

0x454d8940…cfe7

0x34b655…2a6f

6 touches
3 conflicts

0x344dbdb0…0cc0

0x34b655…2a6f

4 touches
1 conflict

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

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

3 conflicts on slot 0xda7f9bd20d…e9e332

← previous block·next block →recent activity