← previous blocknext block →recent activity

Analyzing

Block #74,229,956

36 transactions · 30 stateful · 2026-05-13 02:27:33 UTC

Parallelism

78/100

Blocked

67%

Avg conflicts / tx

1.53

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,229,956  ·  36 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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x8a0d91a0…2b15

0x34b655…2a6f

8 touches
6 conflicts

0x37ed0601…19f5

0x34b655…2a6f

8 touches
6 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0xbfca3cd0…5023

0x34b655…2a6f

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: 0x34b6552d…112a6f

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity