← previous blocknext block →recent activity

Analyzing

Block #74,917,985

43 transactions · 24 stateful · 2026-05-16 06:59:18 UTC

Parallelism

65/100

Blocked

79%

Avg conflicts / tx

2.63

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #74,917,985  ·  43 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0x0c356eb0…864b

0xd32edf…ff58

29 touches
105 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

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

105 conflicts on slot 0x0c356eb03f…e0864b

← previous block·next block →recent activity