← previous blocknext block →recent activity

Analyzing

Block #74,760,114

25 transactions · 21 stateful · 2026-05-15 13:25:49 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.16

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,760,114  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xc84f3776…edc1

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xb538c6fa…9ae7

0x1b6862…e19c

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

21 conflicts on slot 0xc84f3776a9…e7edc1

← previous block·next block →recent activity