← previous blocknext block →recent activity

Analyzing

Block #74,762,055

40 transactions · 28 stateful · 2026-05-15 13:38:50 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

1.1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,762,055  ·  40 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb9868b52…c77f

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

8 touches
6 conflicts

0x5553f577…f9ee

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

8 touches
6 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity