← previous blocknext block →recent activity

Analyzing

Block #74,389,846

30 transactions · 16 stateful · 2026-05-13 20:11:02 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,389,846  ·  30 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

0xa41dac6c…7662

0xd32edf…ff58

13 touches
21 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x291670b4…1055

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 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

21 conflicts on slot 0xa41dac6c2b…747662

← previous block·next block →recent activity