← previous blocknext block →recent activity

Analyzing

Block #75,507,620

10 transactions · 8 stateful · 2026-05-19 00:44:45 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,507,620  ·  10 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

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x37d49489…9309

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x10d80fee…dbda

0x1d1325…2305

2 touches
0 conflicts

0x3484c9df…bfd5

0x1d1325…2305

2 touches
0 conflicts

0x8cf3d245…1d0d

0x1d1325…2305

2 touches
0 conflicts

0xdb067026…9eb8

0x1d1325…2305

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: 0x34b6552d…112a6f

1 conflict on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity