← previous blocknext block →recent activity

Analyzing

Block #84,060,914

39 transactions · 32 stateful · 2026-06-27 15:40:00 UTC

Parallelism

72/100

Blocked

72%

Avg conflicts / tx

2.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #84,060,914  ·  39 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

22 touches
55 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

14 touches
21 conflicts

0x0efc210e…70ab

0x34b655…2a6f

10 touches
10 conflicts

0xe1e58d05…117f

0x34b655…2a6f

10 touches
10 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

10 touches
10 conflicts

0xe02484a6…c32e

0xc8689a…ee79

8 touches
6 conflicts

0x63f848df…7824

0x34b655…2a6f

8 touches
6 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

8 touches
6 conflicts

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

55 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity