← previous blocknext block →recent activity

Analyzing

Block #74,218,456

26 transactions · 22 stateful · 2026-05-13 01:11:08 UTC

Parallelism

69/100

Blocked

68%

Avg conflicts / tx

1.88

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,218,456  ·  26 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

0x67329216…a4f8

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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

28 conflicts on slot 0x67329216b4…1ca4f8

← previous block·next block →recent activity