← previous blocknext block →recent activity

Analyzing

Block #74,410,486

27 transactions · 22 stateful · 2026-05-13 22:28:32 UTC

Parallelism

74/100

Blocked

45%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,410,486  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x77336153…8818

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x999d60fe…4992

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x44ad89ba…cf83

0x0cc9b2…7777

4 touches
1 conflict

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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 0x77336153c9…4d8818

← previous block·next block →recent activity