← previous blocknext block →recent activity

Analyzing

Block #84,335,895

21 transactions · 17 stateful · 2026-06-28 22:11:34 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,335,895  ·  21 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

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x1b1df992…40eb

0x34b655…2a6f

4 touches
1 conflict

0x23ab8481…52d5

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x5e156077…a91a

0x34b655…2a6f

4 touches
1 conflict

0xb6ed511f…6b68

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

3 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity