← previous blocknext block →recent activity

Analyzing

Block #75,107,318

19 transactions · 16 stateful · 2026-05-17 04:04:35 UTC

Parallelism

84/100

Blocked

44%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,107,318  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xe5060fe3…ebe4

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

3 conflicts on slot 0x0000000000…000019

← previous block·next block →recent activity