← previous blocknext block →recent activity

Analyzing

Block #74,744,935

41 transactions · 26 stateful · 2026-05-15 11:44:06 UTC

Parallelism

76/100

Blocked

62%

Avg conflicts / tx

1.32

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,744,935  ·  41 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

0x5ca58418…09ad

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0x17a7f697…dcb2

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0019

0x1b6862…e19c

12 touches
15 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

28 conflicts on slot 0x5ca58418df…a909ad

← previous block·next block →recent activity