← previous blocknext block →recent activity

Analyzing

Block #74,919,684

39 transactions · 24 stateful · 2026-05-16 07:10:40 UTC

Parallelism

80/100

Blocked

58%

Avg conflicts / tx

1.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,919,684  ·  39 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x4c53ac1e…78d7

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

6 touches
3 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

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

28 conflicts on slot 0x4c53ac1e56…4d78d7

← previous block·next block →recent activity