← previous blocknext block →recent activity

Analyzing

Block #74,218,465

13 transactions · 9 stateful · 2026-05-13 01:11:11 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,218,465  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x3bad9a73…4341

0xd32edf…ff58

5 touches
3 conflicts

0x0e8a2bd3…ef4c

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0x99f080dc…58c1

0x34b655…2a6f

4 touches
1 conflict

0xaa3492db…3703

0x34b655…2a6f

4 touches
1 conflict

0xaef9058e…322a

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity