← previous blocknext block →recent activity

Analyzing

Block #82,570,448

22 transactions · 17 stateful · 2026-06-20 17:45:22 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,570,448  ·  22 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

0x92813843…c9cb

0x34b655…2a6f

6 touches
3 conflicts

0x08913286…f0df

0x34b655…2a6f

6 touches
3 conflicts

0xe03bbbf2…f240

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x1526b11f…8b21

0x34b655…2a6f

6 touches
3 conflicts

0x772acdf0…f605

0x34b655…2a6f

4 touches
1 conflict

0x8b305a3b…1c35

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0x92813843ce…79c9cb

← previous block·next block →recent activity