← previous blocknext block →recent activity

Analyzing

Block #74,332,234

29 transactions · 17 stateful · 2026-05-13 13:47:43 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

1.03

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,332,234  ·  29 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

0x1f50c8f1…108d

0xd32edf…ff58

15 touches
28 conflicts

0xab2f6eed…254c

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x784d7a94…949c

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

28 conflicts on slot 0x1f50c8f1ec…25108d

← previous block·next block →recent activity