← previous blocknext block →recent activity

Analyzing

Block #84,705,568

20 transactions · 19 stateful · 2026-06-30 15:16:23 UTC

Parallelism

55/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #84,705,568  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xb9bf9bb7…d695

0x40c49f…2af0

4 touches
1 conflict

0xe4fede95…d2cf

0x40c49f…2af0

4 touches
1 conflict

0x0076fb69…767b

0x34b655…2a6f

4 touches
1 conflict

0x03fb27fd…0c06

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 0xfaef08b108…f90696

← previous block·next block →recent activity