← previous blocknext block →recent activity

Analyzing

Block #75,516,373

19 transactions · 11 stateful · 2026-05-19 01:44:42 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,516,373  ·  19 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

0x61c53759…f92a

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

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: 0xd32edf66…9fff58

3 conflicts on slot 0x61c53759a8…35f92a

← previous block·next block →recent activity