← previous blocknext block →recent activity

Analyzing

Block #84,498,443

19 transactions · 18 stateful · 2026-06-29 16:15:18 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.68

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,498,443  ·  19 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

0x3f4dc602…5a18

0x34b655…2a6f

8 touches
6 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

6 touches
3 conflicts

0x0833f1ab…71e7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xd637b3…4160

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

6 touches
3 conflicts

0xb91ec573…01ad

0xd32edf…ff58

5 touches
3 conflicts

0x51087f5a…61f7

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 0x3f4dc6022b…0e5a18

← previous block·next block →recent activity