← previous blocknext block →recent activity

Analyzing

Block #80,240,576

20 transactions · 15 stateful · 2026-06-09 22:52:40 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,240,576  ·  20 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

10 touches
10 conflicts

0x90f07a4f…d932

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0e5f2a94…4732

0x34b655…2a6f

6 touches
3 conflicts

0x3d34f2bd…5d63

0x34b655…2a6f

4 touches
1 conflict

0x445b51c5…0be4

0x34b655…2a6f

4 touches
1 conflict

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x62d6e82b…a750

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity