← previous blocknext block →recent activity

Analyzing

Block #74,646,814

33 transactions · 24 stateful · 2026-05-15 00:49:23 UTC

Parallelism

82/100

Blocked

42%

Avg conflicts / tx

0.55

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,646,814  ·  33 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

0x339145eb…2c36

0xd32edf…ff58

9 touches
10 conflicts

0xd18a8dca…4530

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0xac0c4ad1…de68

0x065c9d…c394

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

10 conflicts on slot 0x339145eb40…162c36

← previous block·next block →recent activity