← previous blocknext block →recent activity

Analyzing

Block #74,240,803

36 transactions · 23 stateful · 2026-05-13 03:39:41 UTC

Parallelism

86/100

Blocked

48%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,240,803  ·  36 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x4f4eae13…9928

0xd32edf…ff58

9 touches
10 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x0baa0dfd…37d2

0x065c9d…c394

7 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

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: 0xd32edf66…9fff58

10 conflicts on slot 0x4f4eae13da…849928

← previous block·next block →recent activity