← previous blocknext block →recent activity

Analyzing

Block #74,761,994

40 transactions · 25 stateful · 2026-05-15 13:38:25 UTC

Parallelism

90/100

Blocked

48%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,761,994  ·  40 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

0xb9b2f910…d3cb

0xd32edf…ff58

7 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

6 conflicts on slot 0xb9b2f910bf…44d3cb

← previous block·next block →recent activity