← previous blocknext block →recent activity

Analyzing

Block #75,501,995

35 transactions · 25 stateful · 2026-05-19 00:06:11 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,501,995  ·  35 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x72b93b8b…1dc9

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0000

0x659bd0…a9da

6 touches
3 conflicts

0x00000000…0001

0x659bd0…a9da

6 touches
3 conflicts

0x7e28e55c…d05c

0x754704…b603

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x019883…2a9a

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

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

28 conflicts on slot 0x72b93b8b15…ad1dc9

← previous block·next block →recent activity