← previous blocknext block →recent activity

Analyzing

Block #80,826,600

27 transactions · 25 stateful · 2026-06-12 16:00:20 UTC

Parallelism

70/100

Blocked

36%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #80,826,600  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0xffa7d0a4…b10a

0x40c49f…2af0

6 touches
3 conflicts

0x0672e4a2…8d1f

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x463be44a…2830

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity