← previous blocknext block →recent activity

Analyzing

Block #75,097,911

12 transactions · 8 stateful · 2026-05-17 03:01:48 UTC

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,097,911  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x4884c43b…462c

0x065c9d…c394

2 touches
0 conflicts

0xbd60c4ab…8e9f

0x065c9d…c394

2 touches
0 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x438cf5f603…8ef077

← previous block·next block →recent activity