← previous blocknext block →recent activity

Analyzing

Block #75,678,488

39 transactions · 22 stateful · 2026-05-19 19:48:00 UTC

Parallelism

77/100

Blocked

59%

Avg conflicts / tx

0.97

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,678,488  ·  39 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x1dca5f7d…38dd

0xd32edf…ff58

15 touches
28 conflicts

0x5f77d607…2c84

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xda6b535e…6d6b

0x1b6862…e19c

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

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: 0xd32edf66…9fff58

28 conflicts on slot 0x1dca5f7d6d…1a38dd

← previous block·next block →recent activity