← previous blocknext block →recent activity

Analyzing

Block #74,427,290

35 transactions · 30 stateful · 2026-05-14 00:20:19 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

2.06

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,427,290  ·  35 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x00000000…0002

0xab3526…fa38

20 touches
45 conflicts

0x075d217a…7426

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x3e04662b…0da4

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

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: 0xab35264b…1cfa38

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity