← previous blocknext block →recent activity

Analyzing

Block #74,429,971

43 transactions · 28 stateful · 2026-05-14 00:38:08 UTC

Parallelism

72/100

Blocked

64%

Avg conflicts / tx

1.77

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,429,971  ·  43 txs across 12 waves  ·  depth 12
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

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

0x1e300ef3…1e87

0xd32edf…ff58

21 touches
55 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

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

55 conflicts on slot 0x1e300ef3df…321e87

← previous block·next block →recent activity