← previous blocknext block →recent activity

Analyzing

Block #74,283,436

14 transactions · 11 stateful · 2026-05-13 08:23:05 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,283,436  ·  14 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

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x30bc42a6…d5bd

0x34b655…2a6f

4 touches
1 conflict

0x31028321…87f2

0x34b655…2a6f

4 touches
1 conflict

0x3817764d…242b

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xb9d2cf2005…28a668

← previous block·next block →recent activity