← previous blocknext block →recent activity

Analyzing

Block #74,914,907

7 transactions · 7 stateful · 2026-05-16 06:38:45 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,914,907  ·  7 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

0x8ffb91fe…7e9c

0x065c9d…c394

4 touches
1 conflict

0xfb74dbb9…be80

0x065c9d…c394

3 touches
1 conflict

0x9b47315b…a5f5

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x1ff79b12…24a3

0x065c9d…c394

2 touches
0 conflicts

0x267326ec…57b6

0x065c9d…c394

2 touches
0 conflicts

0x2c34a644…e3b9

0x065c9d…c394

2 touches
0 conflicts

0x6d3a40d4…8d3d

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x8ffb91fec4…b47e9c

← previous block·next block →recent activity