← previous blocknext block →recent activity

Analyzing

Block #74,430,716

29 transactions · 23 stateful · 2026-05-14 00:43:06 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,430,716  ·  29 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

0xd8ffd34b…9456

0xd32edf…ff58

11 touches
15 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x9a555477…19a8

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

15 conflicts on slot 0xd8ffd34bc3…799456

← previous block·next block →recent activity