← previous blocknext block →recent activity

Analyzing

Block #80,743,835

97 transactions · 17 stateful · 2026-06-12 06:48:28 UTC

Parallelism

93/100

Blocked

47%

Avg conflicts / tx

0.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #80,743,835  ·  97 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf6476f21…3580

0x34b655…2a6f

14 touches
21 conflicts

0x746619c8…1584

0x34b655…2a6f

8 touches
6 conflicts

0x92d4e9d1…b273

0x34b655…2a6f

8 touches
6 conflicts

0x9966da31…0d0f

0x34b655…2a6f

8 touches
6 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0xdee887b3…d41c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 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

21 conflicts on slot 0xf6476f21e7…f83580

← previous block·next block →recent activity