← previous blocknext block →recent activity

Analyzing

Block #75,686,244

15 transactions · 12 stateful · 2026-05-19 20:39:29 UTC

Parallelism

60/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,686,244  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfc6f7c25…8784

0xd32edf…ff58

11 touches
15 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0567fa93…a55d

0x065c9d…c394

2 touches
0 conflicts

0xdfa159d0…1576

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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

15 conflicts on slot 0xfc6f7c258a…ff8784

← previous block·next block →recent activity