← previous blocknext block →recent activity

Analyzing

Block #74,361,148

25 transactions · 18 stateful · 2026-05-13 17:00:01 UTC

Parallelism

72/100

Blocked

67%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,361,148  ·  25 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0x050a4348…907a

0x34b655…2a6f

8 touches
6 conflicts

0xfac43f12…b842

0x34b655…2a6f

8 touches
6 conflicts

0x656bcb43…b144

0xd32edf…ff58

7 touches
6 conflicts

0x6b1259e6…4e0f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity