← previous blocknext block →recent activity

Analyzing

Block #74,459,952

29 transactions · 20 stateful · 2026-05-14 03:57:47 UTC

Parallelism

79/100

Blocked

60%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,459,952  ·  29 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

0xf8016070…dc58

0xd32edf…ff58

9 touches
10 conflicts

0x9a555477…19a8

0x754704…b603

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0004

0x63e48b…53f2

8 touches
6 conflicts

0x6b1259e6…4e11

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

10 conflicts on slot 0xf801607052…8adc58

← previous block·next block →recent activity