← previous blocknext block →recent activity

Analyzing

Block #75,103,897

19 transactions · 16 stateful · 2026-05-17 03:41:43 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,103,897  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x348fda08…7e96

0x065c9d…c394

8 touches
6 conflicts

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xf3b0d85f…52e8

0xd32edf…ff58

5 touches
3 conflicts

0x5f2b44eb…eb9f

0x065c9d…c394

5 touches
3 conflicts

0xd072801f…8c4d

0x065c9d…c394

5 touches
3 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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity