← previous blocknext block →recent activity

Analyzing

Block #74,352,029

19 transactions · 14 stateful · 2026-05-13 15:59:19 UTC

Parallelism

63/100

Blocked

57%

Avg conflicts / tx

0.84

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,352,029  ·  19 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

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0x84143682…30a9

0x34b655…2a6f

8 touches
6 conflicts

0x4f483049…3cc7

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x99f080dc…58c1

0x34b655…2a6f

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

6 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity