← previous blocknext block →recent activity

Analyzing

Block #74,736,254

15 transactions · 12 stateful · 2026-05-15 10:46:15 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,736,254  ·  15 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

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…401e

0x34b655…2a6f

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0xcb643582…2626

0x3bd359…433a

2 touches
0 conflicts

0x041215ce…b041

0x754704…b603

2 touches
0 conflicts

0x9194f4a3…10b8

0x754704…b603

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

1 conflict on slot 0x801a6e5726…c1d85c

← previous block·next block →recent activity