← previous blocknext block →recent activity

Analyzing

Block #74,761,995

30 transactions · 22 stateful · 2026-05-15 13:38:25 UTC

Parallelism

63/100

Blocked

68%

Avg conflicts / tx

1.67

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,761,995  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xe677e02e…1fca

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xc1baef71…0689

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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: 0xd32edf66…9fff58

36 conflicts on slot 0xe677e02e16…ca1fca

← previous block·next block →recent activity