← previous blocknext block →recent activity

Analyzing

Block #74,968,407

22 transactions · 15 stateful · 2026-05-16 12:37:19 UTC

Parallelism

68/100

Blocked

40%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,968,407  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xdc2a3c00…625c

0xd32edf…ff58

13 touches
21 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x490911cc…5fea

0x0c65a0…0852

2 touches
0 conflicts

0xaf41644f…8f2e

0x0c65a0…0852

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

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

21 conflicts on slot 0xdc2a3c005c…5d625c

← previous block·next block →recent activity