← previous blocknext block →recent activity

Analyzing

Block #74,484,564

42 transactions · 25 stateful · 2026-05-14 06:41:30 UTC

Parallelism

83/100

Blocked

48%

Avg conflicts / tx

0.76

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,484,564  ·  42 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

0x5f0d3ef6…752e

0xd32edf…ff58

13 touches
21 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

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

21 conflicts on slot 0x5f0d3ef64a…06752e

← previous block·next block →recent activity