← previous blocknext block →recent activity

Analyzing

Block #74,484,647

37 transactions · 25 stateful · 2026-05-14 06:42:03 UTC

Parallelism

70/100

Blocked

60%

Avg conflicts / tx

1.27

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,484,647  ·  37 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

0x6e04e978…b9af

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0xd53220ed…4738

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…002c

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

10 touches
10 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

28 conflicts on slot 0x6e04e97849…26b9af

← previous block·next block →recent activity