← previous blocknext block →recent activity

Analyzing

Block #74,773,085

33 transactions · 18 stateful · 2026-05-15 14:52:42 UTC

Parallelism

82/100

Blocked

61%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,773,085  ·  33 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x78ae17f2…53be

0x000000…012a

8 touches
6 conflicts

0x61bb41e5…f82b

0xdd0a93…ece5

8 touches
6 conflicts

0x00000000…0005

0xdd0a93…ece5

8 touches
6 conflicts

0x00000000…0004

0xdd0a93…ece5

8 touches
6 conflicts

0x468cb854…6352

0xd32edf…ff58

7 touches
6 conflicts

0x4039b31f…0f4a

0x754704…b603

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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: 0x188d586d…f9ea8e

6 conflicts on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity