← previous blocknext block →recent activity

Analyzing

Block #80,312,381

20 transactions · 16 stateful · 2026-06-10 06:51:25 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.55

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #80,312,381  ·  20 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

0x3d34f2bd…5d63

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x537e2e5b…c3ab

0x34b655…2a6f

6 touches
3 conflicts

0x5d32a251…d929

0x34b655…2a6f

6 touches
3 conflicts

0x82ded54c…06f6

0x34b655…2a6f

4 touches
1 conflict

0x8fbde2b3…9b8f

0x34b655…2a6f

4 touches
1 conflict

0xab981df1…2941

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