← previous blocknext block →recent activity

Analyzing

Block #74,761,206

39 transactions · 32 stateful · 2026-05-15 13:33:05 UTC

Parallelism

67/100

Blocked

69%

Avg conflicts / tx

2.46

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,761,206  ·  39 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xd1824006…4991

0xd32edf…ff58

23 touches
66 conflicts

0xb0e4f69d…34e3

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x631b4113…baa9

0x34b655…2a6f

8 touches
6 conflicts

0x9aee5feb…6a2f

0x065c9d…c394

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

66 conflicts on slot 0xd1824006be…6b4991

← previous block·next block →recent activity