← previous blocknext block →recent activity

Analyzing

Block #74,750,731

19 transactions · 14 stateful · 2026-05-15 12:22:47 UTC

Parallelism

89/100

Blocked

29%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,750,731  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x18d6714b…7a7f

0x065c9d…c394

3 touches
1 conflict

0xc554e2d1…af53

0x065c9d…c394

3 touches
1 conflict

0x7687c04b…6f20

0xd32edf…ff58

3 touches
1 conflict

0x81955a0a…29ee

0x6657d1…8ccc

2 touches
0 conflicts

0xa87599bb…ff37

0x6657d1…8ccc

2 touches
0 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: 0x065c9d28…a9c394

1 conflict on slot 0xf3d7a307cc…f14d63

← previous block·next block →recent activity