← previous blocknext block →recent activity

Analyzing

Block #74,492,254

32 transactions · 20 stateful · 2026-05-14 07:32:42 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.53

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,492,254  ·  32 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

0x76c01288…4de9

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x5e1b1a…7777

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

0x00000000…0000

0x75c3ab…4f0d

4 touches
1 conflict

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 0x76c012883d…fd4de9

← previous block·next block →recent activity