← previous blocknext block →recent activity

Analyzing

Block #74,555,820

19 transactions · 15 stateful · 2026-05-14 14:40:27 UTC

Parallelism

84/100

Blocked

20%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,555,820  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x3c35979a…975d

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

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

1 conflict on slot 0x801a6e5726…c1d85c

← previous block·next block →recent activity