← previous blocknext block →recent activity

Analyzing

Block #74,763,933

45 transactions · 34 stateful · 2026-05-15 13:51:21 UTC

Parallelism

78/100

Blocked

62%

Avg conflicts / tx

1.58

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,763,933  ·  45 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

0xe9799f89…e642

0xd32edf…ff58

19 touches
45 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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

45 conflicts on slot 0xe9799f8924…57e642

← previous block·next block →recent activity