← previous blocknext block →recent activity

Analyzing

Block #75,262,620

21 transactions · 17 stateful · 2026-05-17 21:21:46 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,262,620  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00c73abe…ec87

0x754704…b603

6 touches
3 conflicts

0x613f9dae…c021

0x34b655…2a6f

6 touches
3 conflicts

0xb41699fb…024d

0xd32edf…ff58

5 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0x3d34f2bd…5d63

0x34b655…2a6f

4 touches
1 conflict

0x55192654…91fe

0x34b655…2a6f

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity