← previous blocknext block →recent activity

Analyzing

Block #74,919,820

38 transactions · 27 stateful · 2026-05-16 07:11:35 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.66

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,919,820  ·  38 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x63c824d4…9d38

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

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

21 conflicts on slot 0x63c824d4fe…d79d38

← previous block·next block →recent activity