← previous blocknext block →recent activity

Analyzing

Block #74,285,774

13 transactions · 8 stateful · 2026-05-13 08:38:38 UTC

Parallelism

85/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,285,774  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6c22c70d…33c8

0x34b655…2a6f

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x33cc1278…28a0

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x3817764d…242b

0x34b655…2a6f

2 touches
0 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

2 touches
0 conflicts

0x60ad7285…2ca5

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 0x6c22c70dc6…5133c8

← previous block·next block →recent activity