← previous blocknext block →recent activity

Analyzing

Block #82,796,173

21 transactions · 18 stateful · 2026-06-21 18:54:56 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,796,173  ·  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

0xd8bc53a3…c2fe

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x29d8b89b…7d8e

0x34b655…2a6f

4 touches
1 conflict

0x2bf5914f…c75d

0x34b655…2a6f

4 touches
1 conflict

0x3187fda9…57d9

0x34b655…2a6f

4 touches
1 conflict

0x6c60fbcf…8744

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x7c51d9aa…af39

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 0xd8bc53a346…42c2fe

← previous block·next block →recent activity