← previous blocknext block →recent activity

Analyzing

Block #75,104,542

34 transactions · 17 stateful · 2026-05-17 03:46:01 UTC

Parallelism

65/100

Blocked

65%

Avg conflicts / tx

1.94

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #75,104,542  ·  34 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x0c738e04…3851

0xd32edf…ff58

23 touches
66 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x2f77f0f6…4a92

0x188d58…ea8e

2 touches
0 conflicts

0x2f77f0f6…4a93

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5d

0x188d58…ea8e

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

66 conflicts on slot 0x0c738e046b…1b3851

← previous block·next block →recent activity