← previous blocknext block →recent activity

Analyzing

Block #74,430,652

30 transactions · 18 stateful · 2026-05-14 00:42:41 UTC

Parallelism

87/100

Blocked

39%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,430,652  ·  30 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x88393013…ef98

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity