← previous blocknext block →recent activity

Analyzing

Block #75,301,389

22 transactions · 15 stateful · 2026-05-18 01:41:22 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,301,389  ·  22 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

0xe584def0…958f

0xd32edf…ff58

7 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x438cbba0…b6c6

0x065c9d…c394

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0xe848ca4d…e300

0x065c9d…c394

3 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 0xe584def0fe…37958f

← previous block·next block →recent activity