← previous blocknext block →recent activity

Analyzing

Block #75,163,377

9 transactions · 6 stateful · 2026-05-17 10:18:40 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,163,377  ·  9 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

0x5ee8e24e…8981

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x1b2dca5a…cc04

0x065c9d…c394

2 touches
0 conflicts

0x20ba8dc2…a6e7

0x065c9d…c394

2 touches
0 conflicts

0xd705c7b5…4e12

0x065c9d…c394

2 touches
0 conflicts

0xe2e4c12e…8320

0x065c9d…c394

2 touches
0 conflicts

0xf4740302…14d1

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 0x5ee8e24ea6…978981

← previous block·next block →recent activity