← previous blocknext block →recent activity

Analyzing

Block #74,309,345

31 transactions · 22 stateful · 2026-05-13 11:15:31 UTC

Parallelism

74/100

Blocked

59%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,309,345  ·  31 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xafcc9a14…4952

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb2

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

28 conflicts on slot 0xafcc9a14d3…254952

← previous block·next block →recent activity