← previous blocknext block →recent activity

Analyzing

Block #84,364,836

14 transactions · 12 stateful · 2026-06-29 01:24:33 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,364,836  ·  14 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

0xffc2f21e…b393

0x34b655…2a6f

4 touches
1 conflict

0xbfe63d66…c3e6

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd4b3eaed…38c9

0x34b655…2a6f

4 touches
1 conflict

0xfd4e2262…cd8c

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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 0xffc2f21efe…ecb393

← previous block·next block →recent activity