← previous blocknext block →recent activity

Analyzing

Block #75,309,753

18 transactions · 13 stateful · 2026-05-18 02:37:25 UTC

Parallelism

56/100

Blocked

54%

Avg conflicts / tx

1.56

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,309,753  ·  18 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

0xbd00af20…4905

0xd32edf…ff58

15 touches
28 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0000

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0001

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0003

0x04ddf6…7f33

2 touches
0 conflicts

0x0ef74796…cd18

0x0a3323…0a3c

2 touches
0 conflicts

0xaeabffea…5dd4

0x0a3323…0a3c

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

28 conflicts on slot 0xbd00af205a…5f4905

← previous block·next block →recent activity