← previous blocknext block →recent activity

Analyzing

Block #75,530,447

18 transactions · 12 stateful · 2026-05-19 03:19:57 UTC

Parallelism

83/100

Blocked

42%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,530,447  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xd02d67e5…1d25

0xd32edf…ff58

5 touches
3 conflicts

0xb0e4f69d…34e2

0x1b6862…e19c

4 touches
1 conflict

0x1e393384…1d24

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xd40bddc1…773c

0x34b655…2a6f

4 touches
1 conflict

0xe8f5e33f…719c

0x34b655…2a6f

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity