← previous blocknext block →recent activity

Analyzing

Block #74,400,988

14 transactions · 9 stateful · 2026-05-13 21:25:15 UTC

Parallelism

79/100

Blocked

22%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,400,988  ·  14 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

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0x6f2b871a…04ea

0x18c6fe…7777

2 touches
0 conflicts

0x9995a2da…c008

0x18c6fe…7777

2 touches
0 conflicts

0x0b934e62…3eeb

0x34b655…2a6f

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x1432c04a…50f4

0x34b655…2a6f

2 touches
0 conflicts

0x1dc86774…166a

0x34b655…2a6f

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity