← previous blocknext block →recent activity

Analyzing

Block #74,730,935

31 transactions · 19 stateful · 2026-05-15 10:10:52 UTC

Parallelism

87/100

Blocked

47%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,730,935  ·  31 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

0xa6987031…0e98

0xd32edf…ff58

7 touches
6 conflicts

0x6ab90228…beeb

0x065c9d…c394

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x08943ea2…ed03

0x754704…b603

4 touches
1 conflict

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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 0xa69870314b…d50e98

← previous block·next block →recent activity