← previous blocknext block →recent activity

Analyzing

Block #74,483,239

21 transactions · 16 stateful · 2026-05-14 06:32:39 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,483,239  ·  21 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

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x65bd5770…5ece

0x1b6862…e19c

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0xace81ffa…8b29

0xd32edf…ff58

7 touches
6 conflicts

0x4255feaa…cfe9

0x065c9d…c394

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd9f18d9a…141d

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

6 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity