← previous blocknext block →recent activity

Analyzing

Block #74,223,548

18 transactions · 14 stateful · 2026-05-13 01:45:00 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,223,548  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x30d572a8…a787

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x47b2d2eb…8aa5

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity