← previous blocknext block →recent activity

Analyzing

Block #75,003,474

26 transactions · 12 stateful · 2026-05-16 16:31:52 UTC

Parallelism

77/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,003,474  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd2d08726…dcce

0xd32edf…ff58

11 touches
15 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

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: 0xd32edf66…9fff58

15 conflicts on slot 0xd2d0872660…2cdcce

← previous block·next block →recent activity