← previous blocknext block →recent activity

Analyzing

Block #84,359,710

25 transactions · 21 stateful · 2026-06-29 00:50:24 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,359,710  ·  25 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

0x3614b052…4e53

0x34b655…2a6f

4 touches
1 conflict

0x454d8940…cfe7

0x34b655…2a6f

4 touches
1 conflict

0x75cdffd8…c217

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x33b6f9ba…30e0

0x065c9d…c394

4 touches
1 conflict

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0xd33e70b0…1515

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

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

1 conflict on slot 0x3614b05268…c54e53

← previous block·next block →recent activity