← previous blocknext block →recent activity

Analyzing

Block #74,744,925

50 transactions · 36 stateful · 2026-05-15 11:44:02 UTC

Parallelism

76/100

Blocked

64%

Avg conflicts / tx

1.84

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,744,925  ·  50 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

0x95f31e0d…dd95

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…0019

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xea57afd0…4232

0x34b655…2a6f

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

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

66 conflicts on slot 0x95f31e0dc8…e2dd95

← previous block·next block →recent activity