← previous blocknext block →recent activity

Analyzing

Block #74,899,489

16 transactions · 15 stateful · 2026-05-16 04:55:57 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,899,489  ·  16 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

0xd61b999e…fa2d

0x188d58…ea8e

4 touches
1 conflict

0xd61b999e…fa2e

0x188d58…ea8e

4 touches
1 conflict

0x95de2003…c7de

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x4aa4f53b…899f

0x188d58…ea8e

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: 0x188d586d…f9ea8e

1 conflict on slot 0xd61b999e44…9dfa2d

← previous block·next block →recent activity