← previous blocknext block →recent activity

Analyzing

Block #75,468,366

19 transactions · 16 stateful · 2026-05-18 20:17:31 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,468,366  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xba5743c7…21bf

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x86ee2e68…5c32

0xd32edf…ff58

5 touches
3 conflicts

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0xaeb5864c…7679

0x2a68ba…90c5

4 touches
1 conflict

0xa617fb2b…8241

0x065c9d…c394

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: 0x1b68626d…2de19c

3 conflicts on slot 0xba5743c7a6…7321bf

← previous block·next block →recent activity