← previous blocknext block →recent activity

Analyzing

Block #84,081,455

21 transactions · 18 stateful · 2026-06-27 17:56:42 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,081,455  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x9966da31…0d0f

0x34b655…2a6f

6 touches
3 conflicts

0x4fd07709…6eb5

0x34b655…2a6f

6 touches
3 conflicts

0x6f132c01…cdcd

0x34b655…2a6f

6 touches
3 conflicts

0x62ffc7ed…2462

0x34b655…2a6f

6 touches
3 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

6 touches
3 conflicts

0x170e4e4c…2b90

0x34b655…2a6f

6 touches
3 conflicts

0x7506443a…4820

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity