← previous blocknext block →recent activity

Analyzing

Block #74,462,063

29 transactions · 16 stateful · 2026-05-14 04:11:49 UTC

Parallelism

93/100

Blocked

6%

Avg conflicts / tx

0.03

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,462,063  ·  29 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

0xd037c134…47b0

0x699abc…6a3b

4 touches
1 conflict

0xe54fabbb…6088

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5d

0x188d58…ea8e

2 touches
0 conflicts

0x4aa4f53b…899f

0x188d58…ea8e

2 touches
0 conflicts

0x4aa4f53b…89a0

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: 0x699abc15…c86a3b

1 conflict on slot 0xd037c134e2…db47b0

← previous block·next block →recent activity